Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc8352208c3c44e49ebe2f226c593c4a08211c411123a4bdea8af2d8b45782cb

Tx prefix hash: 656a85dad79219586696ad1ac08cd0f88f6b1b879ae5dfefca18a9937edbcd27
Tx public key: 7d62f059a03a73dccb8291079c90490072525880532a8faa9c27dc5d17039d30
Timestamp: 1718151644 Timestamp [UCT]: 2024-06-12 00:20:44 Age [y:d:h:m:s]: 00:299:05:35:48
Block: 1042235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213824 RingCT/type: yes/0
Extra: 017d62f059a03a73dccb8291079c90490072525880532a8faa9c27dc5d17039d3002110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c171946f4ccc4c1ffedc8142b83234a165257430520f7eac9ec9b3c980d9a913 0.600000000000 1511104 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": 1042245, "vin": [ { "gen": { "height": 1042235 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c171946f4ccc4c1ffedc8142b83234a165257430520f7eac9ec9b3c980d9a913" } } ], "extra": [ 1, 125, 98, 240, 89, 160, 58, 115, 220, 203, 130, 145, 7, 156, 144, 73, 0, 114, 82, 88, 128, 83, 42, 143, 170, 156, 39, 220, 93, 23, 3, 157, 48, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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