Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 656cd8a1a21d08ea8629e7864659e79043633f6ee52eed6f8ffa560c522d4b74

Tx prefix hash: 863ec23a962b52ab76ded05713d4af3ed0d9187c636d3ef362a5fa538e4374fb
Tx public key: 9a275feaa857265cc310b5bf08f6b9b94022ccb3b761f1fd2fb57943eb33edfd
Timestamp: 1697112175 Timestamp [UCT]: 2023-10-12 12:02:55 Age [y:d:h:m:s]: 01:188:18:08:33
Block: 868021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395931 RingCT/type: yes/0
Extra: 019a275feaa857265cc310b5bf08f6b9b94022ccb3b761f1fd2fb57943eb33edfd02110000000d75e3f0e9000000000000000000

1 output(s) for total of 0.816368285000 dcy

stealth address amount amount idx
00: 7b1ce69da43d4e44cdc5e1a3c2e27c6d2818b42ab696f430dacbed708294ac56 0.816368285000 1322768 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": 868031, "vin": [ { "gen": { "height": 868021 } } ], "vout": [ { "amount": 816368285, "target": { "key": "7b1ce69da43d4e44cdc5e1a3c2e27c6d2818b42ab696f430dacbed708294ac56" } } ], "extra": [ 1, 154, 39, 95, 234, 168, 87, 38, 92, 195, 16, 181, 191, 8, 246, 185, 185, 64, 34, 204, 179, 183, 97, 241, 253, 47, 181, 121, 67, 235, 51, 237, 253, 2, 17, 0, 0, 0, 13, 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