Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0e43c4dfbfab92b04bcb0238e31483c911a79c8e0dc60a51435a3cbffd6883c

Tx prefix hash: bd52eb3d5d1f4c3f269b68cd0a7d7c0cb7fba9eb48d353598be00c858b71efc6
Tx public key: e9fb16f71457241eaf796d23c191bc794dcc9fef5797be301e9a8f19fce5e443
Timestamp: 1731417615 Timestamp [UCT]: 2024-11-12 13:20:15 Age [y:d:h:m:s]: 00:144:14:25:39
Block: 1152122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103168 RingCT/type: yes/0
Extra: 01e9fb16f71457241eaf796d23c191bc794dcc9fef5797be301e9a8f19fce5e443021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d198edd3c315b2a363bc0a89a48fe9c9b2341dcbc68a7c7f9b962bb5b49e24bd 0.600000000000 1637713 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": 1152132, "vin": [ { "gen": { "height": 1152122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d198edd3c315b2a363bc0a89a48fe9c9b2341dcbc68a7c7f9b962bb5b49e24bd" } } ], "extra": [ 1, 233, 251, 22, 247, 20, 87, 36, 30, 175, 121, 109, 35, 193, 145, 188, 121, 77, 204, 159, 239, 87, 151, 190, 48, 30, 154, 143, 25, 252, 229, 228, 67, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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