Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bd9b1670c51f2003168c0818d27caf6fd9ae65c7f41f865c204b5d3e8912cd3

Tx prefix hash: a0a195f31dfa4b2a971803b58161ff5fc9e51f6541c04507a623e728accd1b49
Tx public key: 6614a96aff861c691af508a50d98c60b6480b6abb6fa0f5ee5f4d44f8d786bae
Timestamp: 1723081654 Timestamp [UCT]: 2024-08-08 01:47:34 Age [y:d:h:m:s]: 00:159:16:39:57
Block: 1083100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114246 RingCT/type: yes/0
Extra: 016614a96aff861c691af508a50d98c60b6480b6abb6fa0f5ee5f4d44f8d786bae021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51d100192d503837b49259cdbec8819d591171eb75fe12ecb4ca5167f328c81f 0.600000000000 1556935 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": 1083110, "vin": [ { "gen": { "height": 1083100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51d100192d503837b49259cdbec8819d591171eb75fe12ecb4ca5167f328c81f" } } ], "extra": [ 1, 102, 20, 169, 106, 255, 134, 28, 105, 26, 245, 8, 165, 13, 152, 198, 11, 100, 128, 182, 171, 182, 250, 15, 94, 229, 244, 212, 79, 141, 120, 107, 174, 2, 17, 0, 0, 0, 1, 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