Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7ab31fd574e528e0f592b050ef9d7b956efa7cd6d35a7987e6bc0ae1b5bc4c1

Tx prefix hash: 1e0a7d883d5504361ccdabddf5d705612ef247cae11583cdfeda817ce909c1c5
Tx public key: 3dc6f0f5582adbefd5a43d166e6868ffe65f23eb39abf60df569658cbc87c68d
Timestamp: 1762964231 Timestamp [UCT]: 2025-11-12 16:17:11 Age [y:d:h:m:s]: 00:041:07:15:59
Block: 1410623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29560 RingCT/type: yes/0
Extra: 013dc6f0f5582adbefd5a43d166e6868ffe65f23eb39abf60df569658cbc87c68d021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3539def95b1ba4639ccf39766df24252cb406845220b12b5aa66c078c43723d0 0.600000000000 1899076 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": 1410633, "vin": [ { "gen": { "height": 1410623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3539def95b1ba4639ccf39766df24252cb406845220b12b5aa66c078c43723d0" } } ], "extra": [ 1, 61, 198, 240, 245, 88, 42, 219, 239, 213, 164, 61, 22, 110, 104, 104, 255, 230, 95, 35, 235, 57, 171, 246, 13, 245, 105, 101, 140, 188, 135, 198, 141, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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