Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d49e137d4f5998578a0530ae2ee2345aef4d4f68d9954478fd1b812ce846cfcc

Tx prefix hash: 29c556e55c51971cbefa5910031f9a23f0c407c3d560cf703c932ab1e5175ef1
Tx public key: 7965fa80dbf346ac7dcc1feb790983b3150b9e68383681d16cba930e60d1331b
Timestamp: 1736106498 Timestamp [UCT]: 2025-01-05 19:48:18 Age [y:d:h:m:s]: 00:093:08:43:52
Block: 1190953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66505 RingCT/type: yes/0
Extra: 017965fa80dbf346ac7dcc1feb790983b3150b9e68383681d16cba930e60d1331b0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96c3588f8de89a0945cdad8d3d2c7b20a7380c1278b38fecf7d8f5d02c6e0f4b 0.600000000000 1677476 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": 1190963, "vin": [ { "gen": { "height": 1190953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96c3588f8de89a0945cdad8d3d2c7b20a7380c1278b38fecf7d8f5d02c6e0f4b" } } ], "extra": [ 1, 121, 101, 250, 128, 219, 243, 70, 172, 125, 204, 31, 235, 121, 9, 131, 179, 21, 11, 158, 104, 56, 54, 129, 209, 108, 186, 147, 14, 96, 209, 51, 27, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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