Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45f3fd5ffcb51ce0909adb1a9f40c40ce7cf3227d33b4244a32161f9daea7c7a

Tx prefix hash: ed8b8e0ef4322af20ffa712170a76ffd2383d778ff9a8c3d7787915b84825b9d
Tx public key: 1e9b62801935eceaf95acf85ce9bc5b385cb32d8756396f402e87e0c3f3e46b8
Timestamp: 1726644866 Timestamp [UCT]: 2024-09-18 07:34:26 Age [y:d:h:m:s]: 00:212:22:40:21
Block: 1112641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152020 RingCT/type: yes/0
Extra: 011e9b62801935eceaf95acf85ce9bc5b385cb32d8756396f402e87e0c3f3e46b802110000000591e13c04000000000000000000

1 output(s) for total of 0.608000000000 dcy

stealth address amount amount idx
00: 89c47d0dfa5a8e1a316a5eccdf56f2daed4b368e1f9f94d316f8cdc19dedf250 0.608000000000 1592032 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": 1112651, "vin": [ { "gen": { "height": 1112641 } } ], "vout": [ { "amount": 608000000, "target": { "key": "89c47d0dfa5a8e1a316a5eccdf56f2daed4b368e1f9f94d316f8cdc19dedf250" } } ], "extra": [ 1, 30, 155, 98, 128, 25, 53, 236, 234, 249, 90, 207, 133, 206, 155, 197, 179, 133, 203, 50, 216, 117, 99, 150, 244, 2, 232, 126, 12, 63, 62, 70, 184, 2, 17, 0, 0, 0, 5, 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