Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cae3a65c62e37d8325e9d28cbcf6a70ee6f02626a657b2dec29bc011ef3faacf

Tx prefix hash: 152753d88b046279073c8d8c3e7afb02ac53d7a05fb0b9bf88a9a04cc3c47271
Tx public key: 9b0f7be506bb3f6fe98e1965bf37a9cf743e27dc25873adaa63fe577ed32314e
Timestamp: 1707860480 Timestamp [UCT]: 2024-02-13 21:41:20 Age [y:d:h:m:s]: 00:350:02:13:52
Block: 956917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250353 RingCT/type: yes/0
Extra: 019b0f7be506bb3f6fe98e1965bf37a9cf743e27dc25873adaa63fe577ed32314e02110000000e7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2829a4ac4c24ec027a7285acb4264b370da634620b93bb0afd1ec46712a50663 0.600000000000 1416229 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": 956927, "vin": [ { "gen": { "height": 956917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2829a4ac4c24ec027a7285acb4264b370da634620b93bb0afd1ec46712a50663" } } ], "extra": [ 1, 155, 15, 123, 229, 6, 187, 63, 111, 233, 142, 25, 101, 191, 55, 169, 207, 116, 62, 39, 220, 37, 135, 58, 218, 166, 63, 229, 119, 237, 50, 49, 78, 2, 17, 0, 0, 0, 14, 122, 156, 244, 199, 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