Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 890e0f68860443c8cd6db5486cd2e13bbfad79c165504a4b78b05122ab9012ba

Tx prefix hash: 97292346d70d0363a1a77d340bc8e3a25ae24d1a3ba7fbe81837cc26d6dff9c8
Tx public key: 2c6e02021a44b1afc251e9ba635b7af0fb52a4bfe9accf877a950e85c273cb03
Timestamp: 1740942030 Timestamp [UCT]: 2025-03-02 19:00:30 Age [y:d:h:m:s]: 00:331:21:46:33
Block: 1230711 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234881 RingCT/type: yes/0
Extra: 012c6e02021a44b1afc251e9ba635b7af0fb52a4bfe9accf877a950e85c273cb030211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cab3878dabf29c040cac8e7543246e8df36310febe10d60a8ab87f7ba1709788 0.600000000000 1717610 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": 1230721, "vin": [ { "gen": { "height": 1230711 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cab3878dabf29c040cac8e7543246e8df36310febe10d60a8ab87f7ba1709788" } } ], "extra": [ 1, 44, 110, 2, 2, 26, 68, 177, 175, 194, 81, 233, 186, 99, 91, 122, 240, 251, 82, 164, 191, 233, 172, 207, 135, 122, 149, 14, 133, 194, 115, 203, 3, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 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