Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40c0e4a7db03a5f5bd3c2f2494288f89bf2d8e6456ba441482fdf1f1de13128a

Tx prefix hash: c5a67af5b8066c21791bfc147ca2416f3276c6387e38c2347f274ae3b955f9da
Tx public key: 4d760c512f5d1968e36754a588ecc19e7efe0ae22d963794f663081035b65db2
Timestamp: 1683701966 Timestamp [UCT]: 2023-05-10 06:59:26 Age [y:d:h:m:s]: 01:244:15:05:58
Block: 756878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 436279 RingCT/type: yes/0
Extra: 014d760c512f5d1968e36754a588ecc19e7efe0ae22d963794f663081035b65db202110000000233af99f4000000000000000000

1 output(s) for total of 1.906115373000 dcy

stealth address amount amount idx
00: 5bcae2da267f14160fcd72db5b99e60df7a89053992570248d0d8800feaa8c53 1.906115373000 1205271 of 0

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": 756888, "vin": [ { "gen": { "height": 756878 } } ], "vout": [ { "amount": 1906115373, "target": { "key": "5bcae2da267f14160fcd72db5b99e60df7a89053992570248d0d8800feaa8c53" } } ], "extra": [ 1, 77, 118, 12, 81, 47, 93, 25, 104, 227, 103, 84, 165, 136, 236, 193, 158, 126, 254, 10, 226, 45, 150, 55, 148, 246, 99, 8, 16, 53, 182, 93, 178, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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