Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b227986ad53ce57f7826ff8da293e883772329947dc4416056f9f7abf2a7e5ef

Tx prefix hash: a41d5998ec9df9b11d5ff99e1ed42a7c525fbd4b94c5f4cf29e18fc098b7af6a
Tx public key: 0bcc3d1fb2d33cc20470da56f1dcf053eba3574ffd22dfb1d1d6772e1d49ee9e
Timestamp: 1706342305 Timestamp [UCT]: 2024-01-27 07:58:25 Age [y:d:h:m:s]: 01:033:12:59:17
Block: 944297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285038 RingCT/type: yes/0
Extra: 010bcc3d1fb2d33cc20470da56f1dcf053eba3574ffd22dfb1d1d6772e1d49ee9e0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 458e35bb23100dc054ff652959a71d0f33cdf56b4d41aac4d6d2ad03846689e6 0.600000000000 1402533 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": 944307, "vin": [ { "gen": { "height": 944297 } } ], "vout": [ { "amount": 600000000, "target": { "key": "458e35bb23100dc054ff652959a71d0f33cdf56b4d41aac4d6d2ad03846689e6" } } ], "extra": [ 1, 11, 204, 61, 31, 178, 211, 60, 194, 4, 112, 218, 86, 241, 220, 240, 83, 235, 163, 87, 79, 253, 34, 223, 177, 209, 214, 119, 46, 29, 73, 238, 158, 2, 17, 0, 0, 0, 1, 0, 17, 5, 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