Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48742b34f1a2743f9de6cf15eed752711d96e4a512c5b06a41b571ec9909070c

Tx prefix hash: 0e8f62ee356094de341bea988a727a55dfc736f0c2d0e849b2b908f6b53fa0c7
Tx public key: 76099adb779b995dbb24d99aa9bf18c4aaa0b1e01dfa8bc520cf261d9f74d09d
Timestamp: 1750882831 Timestamp [UCT]: 2025-06-25 20:20:31 Age [y:d:h:m:s]: 00:143:08:13:39
Block: 1312716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100423 RingCT/type: yes/0
Extra: 0176099adb779b995dbb24d99aa9bf18c4aaa0b1e01dfa8bc520cf261d9f74d09d021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db660a83b6861e790ea0e1542f54d603c5c5c552c6a33fd5d3edb4400e79f4c0 0.600000000000 1800351 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": 1312726, "vin": [ { "gen": { "height": 1312716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db660a83b6861e790ea0e1542f54d603c5c5c552c6a33fd5d3edb4400e79f4c0" } } ], "extra": [ 1, 118, 9, 154, 219, 119, 155, 153, 93, 187, 36, 217, 154, 169, 191, 24, 196, 170, 160, 177, 224, 29, 250, 139, 197, 32, 207, 38, 29, 159, 116, 208, 157, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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