Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24abde959c9cfef08397c8ed3dcdbc3166d8dc8c33c91aead24c9ca7c3ef2f30

Tx prefix hash: c62fd2abbc8eb47a79a7a1b2d6899993c7648b63c7ffbfea344ccdaa48a2cec8
Tx public key: 5d8749e571b8b280d2a0c8ca66a18d0cfeff648851014da533eb98f336a39a51
Timestamp: 1578929297 Timestamp [UCT]: 2020-01-13 15:28:17 Age [y:d:h:m:s]: 05:098:16:07:38
Block: 44762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1220656 RingCT/type: yes/0
Extra: 015d8749e571b8b280d2a0c8ca66a18d0cfeff648851014da533eb98f336a39a5102110000003249b77a3d000000000000000000

1 output(s) for total of 436.207622227000 dcy

stealth address amount amount idx
00: df8d4c69f6f6f0f3159d93595c7871eea0d21b28cf1824fb17462202dd182f00 436.207622227000 81541 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": 44772, "vin": [ { "gen": { "height": 44762 } } ], "vout": [ { "amount": 436207622227, "target": { "key": "df8d4c69f6f6f0f3159d93595c7871eea0d21b28cf1824fb17462202dd182f00" } } ], "extra": [ 1, 93, 135, 73, 229, 113, 184, 178, 128, 210, 160, 200, 202, 102, 161, 141, 12, 254, 255, 100, 136, 81, 1, 77, 165, 51, 235, 152, 243, 54, 163, 154, 81, 2, 17, 0, 0, 0, 50, 73, 183, 122, 61, 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