Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b40baf83ab8fdf22fe9b6b3c6b9484ea79290ae283e246ac1fa7e7834bfbeb4e

Tx prefix hash: d1c0dbbab184360feff63edb077997b392345caa28fb4c76cc81285a5dd81552
Tx public key: b7912838a0921d79a3ae9858851f67c0a673bf42d444f49a66b09e8a4ae12ef9
Timestamp: 1722252290 Timestamp [UCT]: 2024-07-29 11:24:50 Age [y:d:h:m:s]: 00:246:00:03:11
Block: 1076228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175710 RingCT/type: yes/0
Extra: 01b7912838a0921d79a3ae9858851f67c0a673bf42d444f49a66b09e8a4ae12ef902110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 842c95de9e355c3e58867c2f8fa17e418d3a18aa99484ecc78c4280f68dd5693 0.600000000000 1548763 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": 1076238, "vin": [ { "gen": { "height": 1076228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "842c95de9e355c3e58867c2f8fa17e418d3a18aa99484ecc78c4280f68dd5693" } } ], "extra": [ 1, 183, 145, 40, 56, 160, 146, 29, 121, 163, 174, 152, 88, 133, 31, 103, 192, 166, 115, 191, 66, 212, 68, 244, 154, 102, 176, 158, 138, 74, 225, 46, 249, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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