Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a5f65eb78664cbe5c1c55166c21b172cfca6ab0fe6917dbc77059cf0ed2f6d1

Tx prefix hash: ea3225a875b645eeba8a3fc5de8d5a9472a19e8faceae1c2afc7e200ab6a868d
Tx public key: 1490fb9faf7cf1148b0e14ebfc75667668558c73c5d7b3df4b42a1e7444f905e
Timestamp: 1713776689 Timestamp [UCT]: 2024-04-22 09:04:49 Age [y:d:h:m:s]: 00:340:10:18:08
Block: 1005961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243362 RingCT/type: yes/0
Extra: 011490fb9faf7cf1148b0e14ebfc75667668558c73c5d7b3df4b42a1e7444f905e02110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 360e744ea884112ba46a88cdcd4ae31bc490aa5fd2d3154e696258b2ed205ac5 0.600000000000 1466827 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": 1005971, "vin": [ { "gen": { "height": 1005961 } } ], "vout": [ { "amount": 600000000, "target": { "key": "360e744ea884112ba46a88cdcd4ae31bc490aa5fd2d3154e696258b2ed205ac5" } } ], "extra": [ 1, 20, 144, 251, 159, 175, 124, 241, 20, 139, 14, 20, 235, 252, 117, 102, 118, 104, 85, 140, 115, 197, 215, 179, 223, 75, 66, 161, 231, 68, 79, 144, 94, 2, 17, 0, 0, 0, 10, 89, 218, 211, 245, 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