Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 187ff27b06c924e1539e24e1e1ddc1781675357a362cf2a5fabdc8efc38aabb5

Tx prefix hash: 46bc5bdb800216b53e7db4c906b8df9faf74223d2dbc0c873c7aba421af0e62f
Tx public key: 20ac79cff0f87800edd9e5156c4f2f403a52661460121f13a238058cb8734325
Timestamp: 1703375057 Timestamp [UCT]: 2023-12-23 23:44:17 Age [y:d:h:m:s]: 01:127:17:25:31
Block: 919722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352429 RingCT/type: yes/0
Extra: 0120ac79cff0f87800edd9e5156c4f2f403a52661460121f13a238058cb873432502110000000d7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 455ef4a18e2b5c32cce4bca10a4cbee8b552987b50abd839a8602ff408528499 0.600000000000 1377398 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": 919732, "vin": [ { "gen": { "height": 919722 } } ], "vout": [ { "amount": 600000000, "target": { "key": "455ef4a18e2b5c32cce4bca10a4cbee8b552987b50abd839a8602ff408528499" } } ], "extra": [ 1, 32, 172, 121, 207, 240, 248, 120, 0, 237, 217, 229, 21, 108, 79, 47, 64, 58, 82, 102, 20, 96, 18, 31, 19, 162, 56, 5, 140, 184, 115, 67, 37, 2, 17, 0, 0, 0, 13, 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