Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37f0f40b6bc711557c396e86693e0a15c8865448bc7f506f9fef3f9d56e1396c

Tx prefix hash: 9130a296a3268201d16e2b5190bd27f9ee65015714aee651dcef18801a5a6b6b
Tx public key: 3cba9da63418040d43af7b4fbbe9f2866fc6e0b159b6f67e48a37d71f3ccaacb
Timestamp: 1648258814 Timestamp [UCT]: 2022-03-26 01:40:14 Age [y:d:h:m:s]: 03:052:01:33:46
Block: 466479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 817412 RingCT/type: yes/0
Extra: 013cba9da63418040d43af7b4fbbe9f2866fc6e0b159b6f67e48a37d71f3ccaacb02110000000506faf294000000000000000000

1 output(s) for total of 17.472766894000 dcy

stealth address amount amount idx
00: 3f5a6c12e56337620a33348ef67886c22c3139e8555f97ffd0237cff12adb3e8 17.472766894000 884802 of 0

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": 466489, "vin": [ { "gen": { "height": 466479 } } ], "vout": [ { "amount": 17472766894, "target": { "key": "3f5a6c12e56337620a33348ef67886c22c3139e8555f97ffd0237cff12adb3e8" } } ], "extra": [ 1, 60, 186, 157, 166, 52, 24, 4, 13, 67, 175, 123, 79, 187, 233, 242, 134, 111, 198, 224, 177, 89, 182, 246, 126, 72, 163, 125, 113, 243, 204, 170, 203, 2, 17, 0, 0, 0, 5, 6, 250, 242, 148, 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