Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: daa71ddd28895ce6cb88bfbbc1f6aae9f267ee0b3c9d993a7a39e963f2ffcd15

Tx prefix hash: 2bb15dd7272db89f6b9bc206d40dc6ceea39d6ac4ef637b3591fe7fd5b5af1ea
Tx public key: 5b3925a0e6156800174b89cd03825e0f2ddfaf3d6cf13d63cc69b7786ac1bdd2
Timestamp: 1755711908 Timestamp [UCT]: 2025-08-20 17:45:08 Age [y:d:h:m:s]: 00:093:01:02:39
Block: 1350734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66405 RingCT/type: yes/0
Extra: 015b3925a0e6156800174b89cd03825e0f2ddfaf3d6cf13d63cc69b7786ac1bdd20211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 250345b037ff121c01faf94fe6c72ec3a17eea3fdb9aab78b60c7ee0706816b3 0.600000000000 1838681 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": 1350744, "vin": [ { "gen": { "height": 1350734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "250345b037ff121c01faf94fe6c72ec3a17eea3fdb9aab78b60c7ee0706816b3" } } ], "extra": [ 1, 91, 57, 37, 160, 230, 21, 104, 0, 23, 75, 137, 205, 3, 130, 94, 15, 45, 223, 175, 61, 108, 241, 61, 99, 204, 105, 183, 120, 106, 193, 189, 210, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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