Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2cdc1330ccd2b26507bb6162507464e928e348722f31b6fef98b65b40f37b19

Tx prefix hash: b60bcd1ae2dbd5f5ab3192801fc548b3a5850148edc55a25e35ad8eb0514f3b1
Tx public key: f7d7a360e162b20d72f75231968f942ad67d3d8581145b155670d2e83a0acc78
Timestamp: 1734712750 Timestamp [UCT]: 2024-12-20 16:39:10 Age [y:d:h:m:s]: 00:015:13:33:11
Block: 1179443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11113 RingCT/type: yes/0
Extra: 01f7d7a360e162b20d72f75231968f942ad67d3d8581145b155670d2e83a0acc780211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3a03b266a4253ee01f3a3cd0d9775ea4d30dc57405b2a2c9d3684f2ebca1548 0.600000000000 1665838 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": 1179453, "vin": [ { "gen": { "height": 1179443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3a03b266a4253ee01f3a3cd0d9775ea4d30dc57405b2a2c9d3684f2ebca1548" } } ], "extra": [ 1, 247, 215, 163, 96, 225, 98, 178, 13, 114, 247, 82, 49, 150, 143, 148, 42, 214, 125, 61, 133, 129, 20, 91, 21, 86, 112, 210, 232, 58, 10, 204, 120, 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