Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbe11c3e2c926e304322b627db91801f4694678740104b3366afac4af01bb192

Tx prefix hash: a825ae70045d13ba231fc9b746a2744a3435e912db51ba6d5704a58dd1ac9de2
Tx public key: e61e8f155fe1f9107564c693a30fd30530b56bae87147a25126e5c0880853c5f
Timestamp: 1696112778 Timestamp [UCT]: 2023-09-30 22:26:18 Age [y:d:h:m:s]: 01:190:15:35:32
Block: 859722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397303 RingCT/type: yes/0
Extra: 01e61e8f155fe1f9107564c693a30fd30530b56bae87147a25126e5c0880853c5f02110000000633af99f4000000000000000000

1 output(s) for total of 0.869729436000 dcy

stealth address amount amount idx
00: a95a3f7cd4a53216cac53e750708b2d37bff40c1d179a2d0d070bed08914c6c0 0.869729436000 1313964 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": 859732, "vin": [ { "gen": { "height": 859722 } } ], "vout": [ { "amount": 869729436, "target": { "key": "a95a3f7cd4a53216cac53e750708b2d37bff40c1d179a2d0d070bed08914c6c0" } } ], "extra": [ 1, 230, 30, 143, 21, 95, 225, 249, 16, 117, 100, 198, 147, 163, 15, 211, 5, 48, 181, 107, 174, 135, 20, 122, 37, 18, 110, 92, 8, 128, 133, 60, 95, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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