Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b572d98fd13caddefd4d5ffc549c5108abfca578b9c957555bdc3a9afd360f35

Tx prefix hash: 3e36051f47fd01fc9fddb5006aa16f5c17d070f815bf932953c4f71113f4edd0
Tx public key: 59ae293cfa70afc5c6896e271a638ff6ed80b71097c3968dc63c361f804a02ee
Timestamp: 1724288968 Timestamp [UCT]: 2024-08-22 01:09:28 Age [y:d:h:m:s]: 01:163:09:28:09
Block: 1093123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375148 RingCT/type: yes/0
Extra: 0159ae293cfa70afc5c6896e271a638ff6ed80b71097c3968dc63c361f804a02ee021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7de05249ebf2c4ff02bb17ff2c7668b8992c921333a875cf7614a3e6cc4b6937 0.600000000000 1568004 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": 1093133, "vin": [ { "gen": { "height": 1093123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7de05249ebf2c4ff02bb17ff2c7668b8992c921333a875cf7614a3e6cc4b6937" } } ], "extra": [ 1, 89, 174, 41, 60, 250, 112, 175, 197, 198, 137, 110, 39, 26, 99, 143, 246, 237, 128, 183, 16, 151, 195, 150, 141, 198, 60, 54, 31, 128, 74, 2, 238, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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