Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86239f4b930b64990f0f53db6bfcbc3a3f75a46514ea77f073729f2f8c283bbc

Tx prefix hash: b58641fb785653137fea27a263c6728b5f9b29afde02a8b24c9f7f817b463efb
Tx public key: 6de6b78fabd23d98eb0b680b054d5269bed1e4c0a0268d7254bd2ff496b220b8
Timestamp: 1736566002 Timestamp [UCT]: 2025-01-11 03:26:42 Age [y:d:h:m:s]: 00:115:15:02:48
Block: 1194749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82447 RingCT/type: yes/0
Extra: 016de6b78fabd23d98eb0b680b054d5269bed1e4c0a0268d7254bd2ff496b220b8021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9686d74481fbe616903103f0f49d4788fa9afd1112727a7d6be39e97e2e6f751 0.600000000000 1681326 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": 1194759, "vin": [ { "gen": { "height": 1194749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9686d74481fbe616903103f0f49d4788fa9afd1112727a7d6be39e97e2e6f751" } } ], "extra": [ 1, 109, 230, 183, 143, 171, 210, 61, 152, 235, 11, 104, 11, 5, 77, 82, 105, 190, 209, 228, 192, 160, 38, 141, 114, 84, 189, 47, 244, 150, 178, 32, 184, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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