Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5578513d6dd6edc0ae772cc75cada8b5f88134e716569912deb4dcc9ca964141

Tx prefix hash: 4e72ae50698c3cd0b704d2d2ac9a2d38958b1ca812f296fbfb5a8a8d0729a776
Tx public key: 8b37911011e053b0d5fc456403c24dc024511e0f7e48974d141faf47253ad6fb
Timestamp: 1741457296 Timestamp [UCT]: 2025-03-08 18:08:16 Age [y:d:h:m:s]: 00:303:06:45:44
Block: 1234992 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214570 RingCT/type: yes/0
Extra: 018b37911011e053b0d5fc456403c24dc024511e0f7e48974d141faf47253ad6fb0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0baaf839cb9115e631932401de57ae3df413d4c45561d742b01c97aade9d5c86 0.600000000000 1721927 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": 1235002, "vin": [ { "gen": { "height": 1234992 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0baaf839cb9115e631932401de57ae3df413d4c45561d742b01c97aade9d5c86" } } ], "extra": [ 1, 139, 55, 145, 16, 17, 224, 83, 176, 213, 252, 69, 100, 3, 194, 77, 192, 36, 81, 30, 15, 126, 72, 151, 77, 20, 31, 175, 71, 37, 58, 214, 251, 2, 17, 0, 0, 0, 1, 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