Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 624634eed6df5048b6407c5ad6e4a1f3e60953cf98e578dbb21bd8c339aed9a0

Tx prefix hash: 4ef53be64dff28df6b71786386ced9eb88df8a5220b0e915b2cffdbcbd0bbb25
Tx public key: d7a2a4c3643d4a40b7ef24838425ab7b325ca788c6351a55637d68109f6514bd
Timestamp: 1720581320 Timestamp [UCT]: 2024-07-10 03:15:20 Age [y:d:h:m:s]: 00:144:04:16:18
Block: 1062377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103183 RingCT/type: yes/0
Extra: 01d7a2a4c3643d4a40b7ef24838425ab7b325ca788c6351a55637d68109f6514bd021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a966c7f044a11a584e76b075b853febebcbe5b7a7f56132d40c22d3bf04324d 0.600000000000 1532878 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": 1062387, "vin": [ { "gen": { "height": 1062377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a966c7f044a11a584e76b075b853febebcbe5b7a7f56132d40c22d3bf04324d" } } ], "extra": [ 1, 215, 162, 164, 195, 100, 61, 74, 64, 183, 239, 36, 131, 132, 37, 171, 123, 50, 92, 167, 136, 198, 53, 26, 85, 99, 125, 104, 16, 159, 101, 20, 189, 2, 17, 0, 0, 0, 2, 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