Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd5f4a55f6e6ecab0daec066d34b59575e69003ea900ab91d86d1e5046d9e6c0

Tx prefix hash: ceb7e6c7c687092d00d775271fddbe0d9119eefa98f0c4bf9a432545233e1fdf
Tx public key: 64625c2cf6917746e5ee0dc9e40fcf225a9daf5d0a99f3413829098ff231a62c
Timestamp: 1750485228 Timestamp [UCT]: 2025-06-21 05:53:48 Age [y:d:h:m:s]: 00:201:06:49:57
Block: 1309555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141784 RingCT/type: yes/0
Extra: 0164625c2cf6917746e5ee0dc9e40fcf225a9daf5d0a99f3413829098ff231a62c021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b8b3ed382e9f51d5fc11de1fb63c0e2734ecdd1ea1f501abf273c9bfa5dedf1 0.600000000000 1797172 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": 1309565, "vin": [ { "gen": { "height": 1309555 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b8b3ed382e9f51d5fc11de1fb63c0e2734ecdd1ea1f501abf273c9bfa5dedf1" } } ], "extra": [ 1, 100, 98, 92, 44, 246, 145, 119, 70, 229, 238, 13, 201, 228, 15, 207, 34, 90, 157, 175, 93, 10, 153, 243, 65, 56, 41, 9, 143, 242, 49, 166, 44, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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