Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71bfbcac0b46a0cde26d9d4bfd5d1786a6ed30ddcfe16cbcc40a16b6c5276467

Tx prefix hash: b7237ed7eed1506721bf28ef12b74bfe52706eedc3be6cef555cdf99ab28e3a5
Tx public key: 190300a722dc3376d32c9d69de0bf4a8d11a3aa674a791f84a4539a577b125e7
Timestamp: 1724071812 Timestamp [UCT]: 2024-08-19 12:50:12 Age [y:d:h:m:s]: 00:229:13:37:03
Block: 1091313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163937 RingCT/type: yes/0
Extra: 01190300a722dc3376d32c9d69de0bf4a8d11a3aa674a791f84a4539a577b125e7021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a037ac9e27c730e2837d68d7303cd80846295a5eeffd02718adbf26bd040f7f8 0.600000000000 1565944 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": 1091323, "vin": [ { "gen": { "height": 1091313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a037ac9e27c730e2837d68d7303cd80846295a5eeffd02718adbf26bd040f7f8" } } ], "extra": [ 1, 25, 3, 0, 167, 34, 220, 51, 118, 211, 44, 157, 105, 222, 11, 244, 168, 209, 26, 58, 166, 116, 167, 145, 248, 74, 69, 57, 165, 119, 177, 37, 231, 2, 17, 0, 0, 0, 4, 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