Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31248678cc6ed43e810c0b47999b374d4087e1aee953fea480c5a133d314cf9d

Tx prefix hash: a3a7102ac447dbb2a0b0f474eebf96e83add4d79ea523232aa3ed66cfec66a22
Tx public key: c587ab42dea530f33bf42662d5699e562d4fe6f34d328cc492e18d09ff671f8f
Timestamp: 1745119763 Timestamp [UCT]: 2025-04-20 03:29:23 Age [y:d:h:m:s]: 00:032:02:36:12
Block: 1265304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22971 RingCT/type: yes/0
Extra: 01c587ab42dea530f33bf42662d5699e562d4fe6f34d328cc492e18d09ff671f8f021100000008dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08aa2b49c69f329ef35a506fc800a1acd2d5ee6f37441dd9f6d31eb961a6bbeb 0.600000000000 1752509 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": 1265314, "vin": [ { "gen": { "height": 1265304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08aa2b49c69f329ef35a506fc800a1acd2d5ee6f37441dd9f6d31eb961a6bbeb" } } ], "extra": [ 1, 197, 135, 171, 66, 222, 165, 48, 243, 59, 244, 38, 98, 213, 105, 158, 86, 45, 79, 230, 243, 77, 50, 140, 196, 146, 225, 141, 9, 255, 103, 31, 143, 2, 17, 0, 0, 0, 8, 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