Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df6d600af2fd5cf032512bc1a6029544015041707b31bc8a7c0103f4014133d1

Tx prefix hash: a1f8bb30cac67217bbd0e5067d4e3662adc0661642714fa5ef0de2b4516b36a8
Tx public key: b5d573d9cb18625f6bfd701c3b9f29ec2773e68902e263607c225f4d9089c508
Timestamp: 1723119544 Timestamp [UCT]: 2024-08-08 12:19:04 Age [y:d:h:m:s]: 00:223:03:37:08
Block: 1083416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159383 RingCT/type: yes/0
Extra: 01b5d573d9cb18625f6bfd701c3b9f29ec2773e68902e263607c225f4d9089c50802110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29726df913b730b950be5df00a57e3cda84da7644a301aff10f7386e3b6b8dbc 0.600000000000 1557327 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": 1083426, "vin": [ { "gen": { "height": 1083416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29726df913b730b950be5df00a57e3cda84da7644a301aff10f7386e3b6b8dbc" } } ], "extra": [ 1, 181, 213, 115, 217, 203, 24, 98, 95, 107, 253, 112, 28, 59, 159, 41, 236, 39, 115, 230, 137, 2, 226, 99, 96, 124, 34, 95, 77, 144, 137, 197, 8, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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