Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fbc8b5301b22f1a779a45cf5cdb9926d8ec562b4628729abc5fa69d3b46d208

Tx prefix hash: dad52d65c47b04995efe49693ada8ee78e31a5a83512734d29df4420131ab9af
Tx public key: 806075e1bd2042d16e9aeecf03fcc2d8a80cef1dfcc6ce3126cf6417e2ef267a
Timestamp: 1722238770 Timestamp [UCT]: 2024-07-29 07:39:30 Age [y:d:h:m:s]: 00:245:21:28:41
Block: 1076117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175643 RingCT/type: yes/0
Extra: 01806075e1bd2042d16e9aeecf03fcc2d8a80cef1dfcc6ce3126cf6417e2ef267a02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e26bd66b796d4e07da49fb96c9896ce131e8dfcee590021e52314c8a240f7b4 0.600000000000 1548652 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": 1076127, "vin": [ { "gen": { "height": 1076117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e26bd66b796d4e07da49fb96c9896ce131e8dfcee590021e52314c8a240f7b4" } } ], "extra": [ 1, 128, 96, 117, 225, 189, 32, 66, 209, 110, 154, 238, 207, 3, 252, 194, 216, 168, 12, 239, 29, 252, 198, 206, 49, 38, 207, 100, 23, 226, 239, 38, 122, 2, 17, 0, 0, 0, 8, 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