Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bbae64eaa9f3c7fa009a1bc2f6cb6a00c26098880de4c198cbace36fa953c5c

Tx prefix hash: fe7cffcf9dd1bff2560196b1daefd16330e34541a8256da1b34f27d34bdb7954
Tx public key: a4cafde321061b6600586e09ebb43671b222ce6fcfe5d6db65deca5d9a83886b
Timestamp: 1676437679 Timestamp [UCT]: 2023-02-15 05:07:59 Age [y:d:h:m:s]: 02:099:00:21:21
Block: 697290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 592402 RingCT/type: yes/0
Extra: 01a4cafde321061b6600586e09ebb43671b222ce6fcfe5d6db65deca5d9a83886b021100000016835e4d22000000000000000000

1 output(s) for total of 3.003230656000 dcy

stealth address amount amount idx
00: 5ccf0ce7f6de242d22ca4fcd451d0f23b043cc0bbd08297f9a4d7227f92e7a83 3.003230656000 1140431 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": 697300, "vin": [ { "gen": { "height": 697290 } } ], "vout": [ { "amount": 3003230656, "target": { "key": "5ccf0ce7f6de242d22ca4fcd451d0f23b043cc0bbd08297f9a4d7227f92e7a83" } } ], "extra": [ 1, 164, 202, 253, 227, 33, 6, 27, 102, 0, 88, 110, 9, 235, 180, 54, 113, 178, 34, 206, 111, 207, 229, 214, 219, 101, 222, 202, 93, 154, 131, 136, 107, 2, 17, 0, 0, 0, 22, 131, 94, 77, 34, 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