Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e8d730a96799fe99728f969ec1fcb8b7d47e390240916f54d356940087508c3

Tx prefix hash: 65f1d974384d06945d5721594cc2de06c72e2474dcfe116e1133f33d7050e7a3
Tx public key: 178aa6d59cb62e470e02a6ca631ca66e1380e9b30618c0d6545afe4a49caeb87
Timestamp: 1745429612 Timestamp [UCT]: 2025-04-23 17:33:32 Age [y:d:h:m:s]: 00:045:09:35:29
Block: 1267862 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32482 RingCT/type: yes/0
Extra: 01178aa6d59cb62e470e02a6ca631ca66e1380e9b30618c0d6545afe4a49caeb8702110000000fdbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1cafa6520d83836331354bf4cd24b9bf7716ccb1ac861e630a9d1e6c392eb1a 0.600000000000 1755091 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": 1267872, "vin": [ { "gen": { "height": 1267862 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1cafa6520d83836331354bf4cd24b9bf7716ccb1ac861e630a9d1e6c392eb1a" } } ], "extra": [ 1, 23, 138, 166, 213, 156, 182, 46, 71, 14, 2, 166, 202, 99, 28, 166, 110, 19, 128, 233, 179, 6, 24, 192, 214, 84, 90, 254, 74, 73, 202, 235, 135, 2, 17, 0, 0, 0, 15, 219, 181, 113, 193, 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