Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b6a0254e0358fe9e5719124d0710f4abbc5a7648c319bf76a76317ba9fa7cc1

Tx prefix hash: 282f9dab383cf93ea2fae9ee8a68ccb5a9caa16ccfd07fc063a4a65f027b0c3a
Tx public key: a28de902d8ca200c596fcd4309a4c510fe51729684e90497ef3b1979e315e1b4
Timestamp: 1582905765 Timestamp [UCT]: 2020-02-28 16:02:45 Age [y:d:h:m:s]: 04:344:15:21:33
Block: 73512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1139685 RingCT/type: yes/0
Extra: 01a28de902d8ca200c596fcd4309a4c510fe51729684e90497ef3b1979e315e1b4021100000006d81c26c0000000000000000000

1 output(s) for total of 350.295652434000 dcy

stealth address amount amount idx
00: 53b4a09a17fe1ea80b083c0c4be182449d4534e22dfdfe9ed906cf4c311d9b50 350.295652434000 135639 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": 73522, "vin": [ { "gen": { "height": 73512 } } ], "vout": [ { "amount": 350295652434, "target": { "key": "53b4a09a17fe1ea80b083c0c4be182449d4534e22dfdfe9ed906cf4c311d9b50" } } ], "extra": [ 1, 162, 141, 233, 2, 216, 202, 32, 12, 89, 111, 205, 67, 9, 164, 197, 16, 254, 81, 114, 150, 132, 233, 4, 151, 239, 59, 25, 121, 227, 21, 225, 180, 2, 17, 0, 0, 0, 6, 216, 28, 38, 192, 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