Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 249b13fe340eafeab0429755760d73181a763ecabf6487504af87d8ca35f02a9

Tx prefix hash: ab650ef8c77530cce14f0b75b4fecbf7ecaf501ee64f9cc0a45806d6e3f8ec8f
Tx public key: 57d41555d56c99fc0a13c5c9c07f19c8b45c2a444e15abf77f40f4b30ee3c681
Timestamp: 1723869571 Timestamp [UCT]: 2024-08-17 04:39:31 Age [y:d:h:m:s]: 00:227:22:36:24
Block: 1089641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162765 RingCT/type: yes/0
Extra: 0157d41555d56c99fc0a13c5c9c07f19c8b45c2a444e15abf77f40f4b30ee3c681021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 288cd71dc9f0843064495c38346196d2d2e45188464b4102a87b4443e83c0a89 0.600000000000 1564264 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": 1089651, "vin": [ { "gen": { "height": 1089641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "288cd71dc9f0843064495c38346196d2d2e45188464b4102a87b4443e83c0a89" } } ], "extra": [ 1, 87, 212, 21, 85, 213, 108, 153, 252, 10, 19, 197, 201, 192, 127, 25, 200, 180, 92, 42, 68, 78, 21, 171, 247, 127, 64, 244, 179, 14, 227, 198, 129, 2, 17, 0, 0, 0, 9, 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