Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9be132f4afe77629cc086a20bd487b17b743df31a4e6ee9c917b5a5ab5d346ca

Tx prefix hash: 2225e1aa5ddc1c71e8bd37028ae9a1039e4be1ac8607cddc22bba7bc8ffd3ee1
Tx public key: 9f557ea39631396b01bf38824fa843fbfae6729dd7158ef62028df9af8a5b825
Timestamp: 1711380228 Timestamp [UCT]: 2024-03-25 15:23:48 Age [y:d:h:m:s]: 00:211:23:12:56
Block: 986113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151776 RingCT/type: yes/0
Extra: 019f557ea39631396b01bf38824fa843fbfae6729dd7158ef62028df9af8a5b8250211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cfec7467742457ee413f8677c420719066798a5d0cae26d4a527e242f1c65e6c 0.600000000000 1446340 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": 986123, "vin": [ { "gen": { "height": 986113 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cfec7467742457ee413f8677c420719066798a5d0cae26d4a527e242f1c65e6c" } } ], "extra": [ 1, 159, 85, 126, 163, 150, 49, 57, 107, 1, 191, 56, 130, 79, 168, 67, 251, 250, 230, 114, 157, 215, 21, 142, 246, 32, 40, 223, 154, 248, 165, 184, 37, 2, 17, 0, 0, 0, 2, 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