Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c7160ea8f4eb2d4ad7d3d7f5fe2c1652ad97d8850eea20d3e4d338739615560

Tx prefix hash: 7a63ba7e976e968187380567252701d6a4d000f34c551bd0f2c3f9216463be1d
Tx public key: 3659790c6abc6073206e6d05e8c4b324ce1f674954c2386e7b3a71bc22815991
Timestamp: 1729978500 Timestamp [UCT]: 2024-10-26 21:35:00 Age [y:d:h:m:s]: 00:028:13:22:54
Block: 1140251 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20387 RingCT/type: yes/0
Extra: 013659790c6abc6073206e6d05e8c4b324ce1f674954c2386e7b3a71bc22815991021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27c1370bc32736fef672f675c048b97a96f3e8c9aa97373a5f89ce2657cb1ff4 0.600000000000 1624046 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": 1140261, "vin": [ { "gen": { "height": 1140251 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27c1370bc32736fef672f675c048b97a96f3e8c9aa97373a5f89ce2657cb1ff4" } } ], "extra": [ 1, 54, 89, 121, 12, 106, 188, 96, 115, 32, 110, 109, 5, 232, 196, 179, 36, 206, 31, 103, 73, 84, 194, 56, 110, 123, 58, 113, 188, 34, 129, 89, 145, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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