Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c5a6b38c6c742333a66c6c3b87d938b053b199d6a5e57813c6cca65e7bc0ab5

Tx prefix hash: 67b5122cfe02941e627f381e9a6a96be304ef426735be58f7044bd8a521419c9
Tx public key: 9a4d99291e1140240b36dfc088fa0077fe86b660a2fbe8a0a0fb64333e205f1b
Timestamp: 1737256056 Timestamp [UCT]: 2025-01-19 03:07:36 Age [y:d:h:m:s]: 00:330:22:05:14
Block: 1200433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234082 RingCT/type: yes/0
Extra: 019a4d99291e1140240b36dfc088fa0077fe86b660a2fbe8a0a0fb64333e205f1b0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25006a0c269a597941233bb85c6e687534768e5ab971c548d9f270abfca247ba 0.600000000000 1687076 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": 1200443, "vin": [ { "gen": { "height": 1200433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25006a0c269a597941233bb85c6e687534768e5ab971c548d9f270abfca247ba" } } ], "extra": [ 1, 154, 77, 153, 41, 30, 17, 64, 36, 11, 54, 223, 192, 136, 250, 0, 119, 254, 134, 182, 96, 162, 251, 232, 160, 160, 251, 100, 51, 62, 32, 95, 27, 2, 17, 0, 0, 0, 2, 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