Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: cd0fb4bc3b180c681797f5f27128eab6a60d40270e88f2ef1e5663896d6661db

Tx prefix hash: 04039371f6a47dbad02565ecca5d1eadfac3515ee900aeb9270ef0efe26948f8
Tx public key: 43521f8e25d5b5b6219fc3510a5c786c9599402a2108bca2ec013c020d3e3ec8
Timestamp: 1723892378 Timestamp [UCT]: 2024-08-17 10:59:38 Age [y:d:h:m:s]: 00:146:17:40:49
Block: 1089838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104954 RingCT/type: yes/0
Extra: 0143521f8e25d5b5b6219fc3510a5c786c9599402a2108bca2ec013c020d3e3ec8021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a540f94e22f4ac2c37971ac5934953b5a65b5e6e013e326889ec0103dac20fe 0.600000000000 1564461 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1089848, "vin": [ { "gen": { "height": 1089838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a540f94e22f4ac2c37971ac5934953b5a65b5e6e013e326889ec0103dac20fe" } } ], "extra": [ 1, 67, 82, 31, 142, 37, 213, 181, 182, 33, 159, 195, 81, 10, 92, 120, 108, 149, 153, 64, 42, 33, 8, 188, 162, 236, 1, 60, 2, 13, 62, 62, 200, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8