Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cd09ad7b1f0fc8d9bce1b0207c3ed8ace3c77976c0bd9dda681a6fd9c83851f

Tx prefix hash: c4f998b7b0bfd1a876e02f94455d772403a4fe5bc7a0f367baf94c093ed906cf
Tx public key: 1eca2fd1c46b3219f584fc452eaed0cb8a53fab47a7a61d7cf87d1d5c4a15613
Timestamp: 1705064640 Timestamp [UCT]: 2024-01-12 13:04:00 Age [y:d:h:m:s]: 01:310:05:44:16
Block: 933724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 480557 RingCT/type: yes/0
Extra: 011eca2fd1c46b3219f584fc452eaed0cb8a53fab47a7a61d7cf87d1d5c4a1561302110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f27dc592563d2b8511970eed56f69517cdcbfb25c1d2ffad2f062f3f7835b54b 0.600000000000 1391694 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": 933734, "vin": [ { "gen": { "height": 933724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f27dc592563d2b8511970eed56f69517cdcbfb25c1d2ffad2f062f3f7835b54b" } } ], "extra": [ 1, 30, 202, 47, 209, 196, 107, 50, 25, 245, 132, 252, 69, 46, 174, 208, 203, 138, 83, 250, 180, 122, 122, 97, 215, 207, 135, 209, 213, 196, 161, 86, 19, 2, 17, 0, 0, 0, 8, 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