Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cec41b920a611af079ce656c9737fefa7a4dab66cedc44ad81fd791c5df2d7f

Tx prefix hash: 35ebf99195692f82186752fac4e54129a022b0bfea94e747046d7f108f4419ce
Tx public key: 5a9ac52b30b8b097a11485ea3d27f01ac4254a893e5575685620f8a27b73df84
Timestamp: 1712292519 Timestamp [UCT]: 2024-04-05 04:48:39 Age [y:d:h:m:s]: 01:033:07:17:08
Block: 993627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284812 RingCT/type: yes/0
Extra: 015a9ac52b30b8b097a11485ea3d27f01ac4254a893e5575685620f8a27b73df840211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00d3bdce8a17a00417ac4f6190ce42bc813f8218698fe71c03a3c1ad4e3a8535 0.600000000000 1454013 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": 993637, "vin": [ { "gen": { "height": 993627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00d3bdce8a17a00417ac4f6190ce42bc813f8218698fe71c03a3c1ad4e3a8535" } } ], "extra": [ 1, 90, 154, 197, 43, 48, 184, 176, 151, 161, 20, 133, 234, 61, 39, 240, 26, 196, 37, 74, 137, 62, 85, 117, 104, 86, 32, 248, 162, 123, 115, 223, 132, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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