Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6017551dc24021335fdee77d23d393a350d3ad9c3c085c6ad49d5d40c5f3aaed

Tx prefix hash: f11da68ca15ba4a0096a38541c544b9a5d3116a0a427ac4017fde6db36c6b649
Tx public key: d2c95ca1816920fe68a4ed7cfdf7be931f5432936508cc162d5d165cb54e26ce
Timestamp: 1707404353 Timestamp [UCT]: 2024-02-08 14:59:13 Age [y:d:h:m:s]: 01:276:21:49:08
Block: 953124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456680 RingCT/type: yes/0
Extra: 01d2c95ca1816920fe68a4ed7cfdf7be931f5432936508cc162d5d165cb54e26ce02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d3f291b69b4a4d074ba446328045f258b391c6be6d41f2c388589b417418a55 0.600000000000 1412292 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": 953134, "vin": [ { "gen": { "height": 953124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d3f291b69b4a4d074ba446328045f258b391c6be6d41f2c388589b417418a55" } } ], "extra": [ 1, 210, 201, 92, 161, 129, 105, 32, 254, 104, 164, 237, 124, 253, 247, 190, 147, 31, 84, 50, 147, 101, 8, 204, 22, 45, 93, 22, 92, 181, 78, 38, 206, 2, 17, 0, 0, 0, 4, 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