Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ec6f14b92c93c657a56a90a7dee3193ed3bb83b8b3bb256c2d8bf1d632fa24a

Tx prefix hash: f4087c9087d54f83a5939e83e5ebf8a6e20d16eb54c9cd4b21a40957fca476b3
Tx public key: 03d5386b2abb580b6af85902ca2debebd824a0e3bc5e2ff38e94298c6a78a1b9
Timestamp: 1659584458 Timestamp [UCT]: 2022-08-04 03:40:58 Age [y:d:h:m:s]: 03:141:10:12:03
Block: 558266 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 880924 RingCT/type: yes/0
Extra: 0103d5386b2abb580b6af85902ca2debebd824a0e3bc5e2ff38e94298c6a78a1b902110000000175e3f0e9000000000000000000

1 output(s) for total of 8.674273571000 dcy

stealth address amount amount idx
00: a0f29e939b6cba0a0e689d3a23b9eaa0ca3a5ffee90f75f901ebe4dbe07f4445 8.674273571000 990332 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": 558276, "vin": [ { "gen": { "height": 558266 } } ], "vout": [ { "amount": 8674273571, "target": { "key": "a0f29e939b6cba0a0e689d3a23b9eaa0ca3a5ffee90f75f901ebe4dbe07f4445" } } ], "extra": [ 1, 3, 213, 56, 107, 42, 187, 88, 11, 106, 248, 89, 2, 202, 45, 235, 235, 216, 36, 160, 227, 188, 94, 47, 243, 142, 148, 41, 140, 106, 120, 161, 185, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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