Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 330c5d33523973ed4ed1cef63fef72ba4184e123381fc33029712c6a364d9dc0

Tx prefix hash: e2bdfb779464239f3ca2730be0e7f5f0b4b05b40f437cc4111693291517bcff4
Tx public key: fa9b5bf5bfb89a12bc6891c2bfa3f7366d75373a4ebd4b56c7488bcba558ae0b
Timestamp: 1735640735 Timestamp [UCT]: 2024-12-31 10:25:35 Age [y:d:h:m:s]: 00:167:04:06:03
Block: 1187091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119211 RingCT/type: yes/0
Extra: 01fa9b5bf5bfb89a12bc6891c2bfa3f7366d75373a4ebd4b56c7488bcba558ae0b021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 462a408006147edc75adb55ae303cf89a8edfbc9254b37b4d7f0e663333170ca 0.600000000000 1673578 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": 1187101, "vin": [ { "gen": { "height": 1187091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "462a408006147edc75adb55ae303cf89a8edfbc9254b37b4d7f0e663333170ca" } } ], "extra": [ 1, 250, 155, 91, 245, 191, 184, 154, 18, 188, 104, 145, 194, 191, 163, 247, 54, 109, 117, 55, 58, 78, 189, 75, 86, 199, 72, 139, 203, 165, 88, 174, 11, 2, 17, 0, 0, 0, 6, 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