Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d504ea7f788acd6de973e552aa0efe215e299e413ebdaa517d14d1eb024c71d0

Tx prefix hash: 29740f1afb6a058f166ce2e758841c3fee81e3523d96b788bbc607b0d2b7e845
Tx public key: b60712c6de4fd91c358d864fa8d0b119c40758c5da2284d37607352ace3c9cbc
Timestamp: 1736705328 Timestamp [UCT]: 2025-01-12 18:08:48 Age [y:d:h:m:s]: 00:065:16:52:26
Block: 1195910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46751 RingCT/type: yes/0
Extra: 01b60712c6de4fd91c358d864fa8d0b119c40758c5da2284d37607352ace3c9cbc0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12368a81deb9590a7f7334c057195270c68b423944afe9775df85d395e1d6a8b 0.600000000000 1682503 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": 1195920, "vin": [ { "gen": { "height": 1195910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12368a81deb9590a7f7334c057195270c68b423944afe9775df85d395e1d6a8b" } } ], "extra": [ 1, 182, 7, 18, 198, 222, 79, 217, 28, 53, 141, 134, 79, 168, 208, 177, 25, 196, 7, 88, 197, 218, 34, 132, 211, 118, 7, 53, 42, 206, 60, 156, 188, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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