Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8045b7ec30b6d6cf038aa6ef3a4ba453359b736deb3aaa1f523c7428ddd5bd8d

Tx prefix hash: d13f345f5f83e74c9abe24e0999b3f8cc434cfdf92bfd9c5c21e65d37a1b86d7
Tx public key: 800cbc9627eae20dd60f6c51ab6d0fa794051f90cf258bcdef9ef1965d99779c
Timestamp: 1707730542 Timestamp [UCT]: 2024-02-12 09:35:42 Age [y:d:h:m:s]: 00:220:07:33:31
Block: 955827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157814 RingCT/type: yes/0
Extra: 01800cbc9627eae20dd60f6c51ab6d0fa794051f90cf258bcdef9ef1965d99779c02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e66e1e3f3e5db30269c311ca0536cefa047edee9da11b05a7aebf4e1e4655a0 0.600000000000 1415127 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": 955837, "vin": [ { "gen": { "height": 955827 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e66e1e3f3e5db30269c311ca0536cefa047edee9da11b05a7aebf4e1e4655a0" } } ], "extra": [ 1, 128, 12, 188, 150, 39, 234, 226, 13, 214, 15, 108, 81, 171, 109, 15, 167, 148, 5, 31, 144, 207, 37, 139, 205, 239, 158, 241, 150, 93, 153, 119, 156, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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