Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39b98829633764feeaae73aa40b343d6d5da8b7148cf616a34e7880ff3d10f3a

Tx prefix hash: 3dddff88e386a66d8848b64eb5e6640fdac7300546eadb42b8a59e7b2b580fd2
Tx public key: d3eae85e9072e32e45327101952c42b3545d8cdf44d6f76038dbb15bb6e905c9
Timestamp: 1765277193 Timestamp [UCT]: 2025-12-09 10:46:33 Age [y:d:h:m:s]: 00:014:04:54:33
Block: 1429791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10160 RingCT/type: yes/0
Extra: 01d3eae85e9072e32e45327101952c42b3545d8cdf44d6f76038dbb15bb6e905c90211000000014e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc72d212044a4c950e1399e976a2f05fa5292cf7a84f1a0b922226fc842b4755 0.600000000000 1918522 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": 1429801, "vin": [ { "gen": { "height": 1429791 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc72d212044a4c950e1399e976a2f05fa5292cf7a84f1a0b922226fc842b4755" } } ], "extra": [ 1, 211, 234, 232, 94, 144, 114, 227, 46, 69, 50, 113, 1, 149, 44, 66, 179, 84, 93, 140, 223, 68, 214, 247, 96, 56, 219, 177, 91, 182, 233, 5, 201, 2, 17, 0, 0, 0, 1, 78, 123, 252, 9, 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