Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1a0cba3fab6883136ff9511e309ce725ec812415fc58b2e736f22d6471b3e94

Tx prefix hash: b0926319a15531fe2add139ddd6cb5a25f0c82a995860ca84a6c9a76618e778c
Tx public key: 1b222cfccdf4a9944b1c4bf9cfb7530a88158e3ef7ac8e29dc963b28f50a6d17
Timestamp: 1629350034 Timestamp [UCT]: 2021-08-19 05:13:54 Age [y:d:h:m:s]: 03:301:02:58:51
Block: 316877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 988536 RingCT/type: yes/0
Extra: 011b222cfccdf4a9944b1c4bf9cfb7530a88158e3ef7ac8e29dc963b28f50a6d1702110000001758045e5b000000000000000000

1 output(s) for total of 54.709527526000 dcy

stealth address amount amount idx
00: e617fee5f27eb5f79b918e2b98532f0b52cbd5896a3f0d9c0d294bd13f76cb39 54.709527526000 659090 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": 316887, "vin": [ { "gen": { "height": 316877 } } ], "vout": [ { "amount": 54709527526, "target": { "key": "e617fee5f27eb5f79b918e2b98532f0b52cbd5896a3f0d9c0d294bd13f76cb39" } } ], "extra": [ 1, 27, 34, 44, 252, 205, 244, 169, 148, 75, 28, 75, 249, 207, 183, 83, 10, 136, 21, 142, 62, 247, 172, 142, 41, 220, 150, 59, 40, 245, 10, 109, 23, 2, 17, 0, 0, 0, 23, 88, 4, 94, 91, 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