Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fb9c2dbe79c3e2220cf127e7c9b062f76c474a90461a0b95d623428c14266f5

Tx prefix hash: b60e0402e29d73d21f66b1130ac334a9e273641817fbed11ae5ba49b4c7de54f
Tx public key: 045129b8f2747a020a1c73dee1a146ce0738f0da685f7e64ae25b714e51297a7
Timestamp: 1752382647 Timestamp [UCT]: 2025-07-13 04:57:27 Age [y:d:h:m:s]: 00:127:20:20:28
Block: 1324376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90097 RingCT/type: yes/0
Extra: 01045129b8f2747a020a1c73dee1a146ce0738f0da685f7e64ae25b714e51297a7021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdd0bc4683241795b5ceaaa7a053d68d9da8f74ca09edd9fbf76e96ab7b83ead 0.600000000000 1812119 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": 1324386, "vin": [ { "gen": { "height": 1324376 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdd0bc4683241795b5ceaaa7a053d68d9da8f74ca09edd9fbf76e96ab7b83ead" } } ], "extra": [ 1, 4, 81, 41, 184, 242, 116, 122, 2, 10, 28, 115, 222, 225, 161, 70, 206, 7, 56, 240, 218, 104, 95, 126, 100, 174, 37, 183, 20, 229, 18, 151, 167, 2, 17, 0, 0, 0, 1, 228, 220, 144, 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