Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70e1928ae67e6dd997891c70e8334bf3a8607670d847b6027e06cc493a6b47e3

Tx prefix hash: f41b0ef2fb6a596945d8c0206dcc0bdd53235f0e1b5771afc26f9d6fdd363c71
Tx public key: 90183ebd04179c4c50483857123f2fc50273e84db53283a92d1e2f79c3a75b12
Timestamp: 1736461804 Timestamp [UCT]: 2025-01-09 22:30:04 Age [y:d:h:m:s]: 00:070:00:28:45
Block: 1193896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49837 RingCT/type: yes/0
Extra: 0190183ebd04179c4c50483857123f2fc50273e84db53283a92d1e2f79c3a75b120211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae95ac6d3d71623eb514dc90ae78afae2c9f68312b1868fac33dae4332df9719 0.600000000000 1680461 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": 1193906, "vin": [ { "gen": { "height": 1193896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae95ac6d3d71623eb514dc90ae78afae2c9f68312b1868fac33dae4332df9719" } } ], "extra": [ 1, 144, 24, 62, 189, 4, 23, 156, 76, 80, 72, 56, 87, 18, 63, 47, 197, 2, 115, 232, 77, 181, 50, 131, 169, 45, 30, 47, 121, 195, 167, 91, 18, 2, 17, 0, 0, 0, 3, 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