Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5938a03b168d22aaaa27dd634b4f795d8c3c02d2ee740cb74267f407fab6eb1b

Tx prefix hash: a58d9ba3765bc113bd512d2c4fc15ad4ca3a129331338d0314bc87ad39a08c7f
Tx public key: f2c0f422e43d8eff499bf0460a469fa3b8496184edbcb45b4a675f7065d69a37
Timestamp: 1658975884 Timestamp [UCT]: 2022-07-28 02:38:04 Age [y:d:h:m:s]: 02:306:00:14:12
Block: 553255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 739934 RingCT/type: yes/0
Extra: 01f2c0f422e43d8eff499bf0460a469fa3b8496184edbcb45b4a675f7065d69a37021100000001faf35c9c000000000000000000

1 output(s) for total of 9.012320864000 dcy

stealth address amount amount idx
00: 659a634d2831042be172fbae3b1415c8d1ca20f6d0ef73245102724d8f3b33e2 9.012320864000 985031 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": 553265, "vin": [ { "gen": { "height": 553255 } } ], "vout": [ { "amount": 9012320864, "target": { "key": "659a634d2831042be172fbae3b1415c8d1ca20f6d0ef73245102724d8f3b33e2" } } ], "extra": [ 1, 242, 192, 244, 34, 228, 61, 142, 255, 73, 155, 240, 70, 10, 70, 159, 163, 184, 73, 97, 132, 237, 188, 180, 91, 74, 103, 95, 112, 101, 214, 154, 55, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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