Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ca1b7046c7e82c907b23e49c18b541ee90c8f20206dfce384915326c05bf33a

Tx prefix hash: 8f3547c5b79ade1f40f96128143b0b277969067f596cd238dd1ea83bb2edd6bc
Tx public key: 2a4e1db7a666edd4f34a6f4daec3e5376386ff81851cd4cc96ee2b4c1a1984c2
Timestamp: 1750914960 Timestamp [UCT]: 2025-06-26 05:16:00 Age [y:d:h:m:s]: 00:219:15:11:03
Block: 1312964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154882 RingCT/type: yes/0
Extra: 012a4e1db7a666edd4f34a6f4daec3e5376386ff81851cd4cc96ee2b4c1a1984c20211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c90ad87d8f2731ac7e2cc3fd260694d4daa6af7003de60c03e489ff534b8cdcf 0.600000000000 1800601 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": 1312974, "vin": [ { "gen": { "height": 1312964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c90ad87d8f2731ac7e2cc3fd260694d4daa6af7003de60c03e489ff534b8cdcf" } } ], "extra": [ 1, 42, 78, 29, 183, 166, 102, 237, 212, 243, 74, 111, 77, 174, 195, 229, 55, 99, 134, 255, 129, 133, 28, 212, 204, 150, 238, 43, 76, 26, 25, 132, 194, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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