Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e2d1d1418fe299a09dd3c057a4d6a1c55e419cf9ef14dee45a0c8690545d881

Tx prefix hash: 804256c72f21c8904d59efe0149d880fc840b5248166559db91853714230f9de
Tx public key: 5eb7f6cf7b069ab3e0eeb754971f259d328a68a5b504c6715ec8976301653f3d
Timestamp: 1759187564 Timestamp [UCT]: 2025-09-29 23:12:44 Age [y:d:h:m:s]: 00:007:23:35:05
Block: 1379323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5706 RingCT/type: yes/0
Extra: 015eb7f6cf7b069ab3e0eeb754971f259d328a68a5b504c6715ec8976301653f3d02110000000797baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f49ba2356bebc3981a17c4ad282ed5e1d5bf86d85228d739e89ec6b3bcfd9bee 0.600000000000 1867420 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": 1379333, "vin": [ { "gen": { "height": 1379323 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f49ba2356bebc3981a17c4ad282ed5e1d5bf86d85228d739e89ec6b3bcfd9bee" } } ], "extra": [ 1, 94, 183, 246, 207, 123, 6, 154, 179, 224, 238, 183, 84, 151, 31, 37, 157, 50, 138, 104, 165, 181, 4, 198, 113, 94, 200, 151, 99, 1, 101, 63, 61, 2, 17, 0, 0, 0, 7, 151, 186, 249, 34, 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