Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b796dc2aa1eefd33c41715f27c5ee0a56913a520b4daf16b4f70d16d53df41a4

Tx prefix hash: 2af35390a2cb4c0d8fed45b2c155debb2936aa67d710c288026f76ba8b7357ec
Tx public key: 8454b23ae46d791fcdbaa22dfc0ea1b9aac194bfc351e1fbc971a19504b9e9c1
Timestamp: 1709793081 Timestamp [UCT]: 2024-03-07 06:31:21 Age [y:d:h:m:s]: 01:036:18:57:22
Block: 972939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287287 RingCT/type: yes/0
Extra: 018454b23ae46d791fcdbaa22dfc0ea1b9aac194bfc351e1fbc971a19504b9e9c102110000000446812bb8000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ea29d894c3b6f687c2975005ee82eba6e6afe9480743345d9f10002fce95dd3 0.600000000000 1432858 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": 972949, "vin": [ { "gen": { "height": 972939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ea29d894c3b6f687c2975005ee82eba6e6afe9480743345d9f10002fce95dd3" } } ], "extra": [ 1, 132, 84, 178, 58, 228, 109, 121, 31, 205, 186, 162, 45, 252, 14, 161, 185, 170, 193, 148, 191, 195, 81, 225, 251, 201, 113, 161, 149, 4, 185, 233, 193, 2, 17, 0, 0, 0, 4, 70, 129, 43, 184, 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