Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40bfae7f23d9f389f65c323c8fa5c04a9336415569282f6f72b6a7d1271cc411

Tx prefix hash: a5b5ab86b1a1e74951bd2de727674abf6ebe156429d4a4d100d8f291179fe477
Tx public key: 1c1c445200d21e0875eac4ac212849e2d05b7e87df0e2aaf083121d274a8e19c
Timestamp: 1726597093 Timestamp [UCT]: 2024-09-17 18:18:13 Age [y:d:h:m:s]: 00:117:08:25:00
Block: 1112244 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83917 RingCT/type: yes/0
Extra: 011c1c445200d21e0875eac4ac212849e2d05b7e87df0e2aaf083121d274a8e19c02110000000d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ae4b8d305cc235956cb74f75e58b6e8d29729810c432be34a22b66f8106376e 0.600000000000 1591499 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": 1112254, "vin": [ { "gen": { "height": 1112244 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ae4b8d305cc235956cb74f75e58b6e8d29729810c432be34a22b66f8106376e" } } ], "extra": [ 1, 28, 28, 68, 82, 0, 210, 30, 8, 117, 234, 196, 172, 33, 40, 73, 226, 208, 91, 126, 135, 223, 14, 42, 175, 8, 49, 33, 210, 116, 168, 225, 156, 2, 17, 0, 0, 0, 13, 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