Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f4031d108858bc79bb2f1c2302ee373912b1ad1f4317d9a90a97ef8459d7c7c

Tx prefix hash: 1d1ca5cb903b4e2bbb50af99a02036409e0ced0927477425d10e81cb0a0884f1
Tx public key: 83f82dbe070cd06f099c006ad38e39b92862ca666e9206dfe4398c58531d1202
Timestamp: 1707012147 Timestamp [UCT]: 2024-02-04 02:02:27 Age [y:d:h:m:s]: 01:051:10:08:36
Block: 949863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297802 RingCT/type: yes/0
Extra: 0183f82dbe070cd06f099c006ad38e39b92862ca666e9206dfe4398c58531d120202110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03beccf5c015e0b1e4d07aa48eaa7f138c5f9d257533f88cb231dcb72dbb4f24 0.600000000000 1408397 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": 949873, "vin": [ { "gen": { "height": 949863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03beccf5c015e0b1e4d07aa48eaa7f138c5f9d257533f88cb231dcb72dbb4f24" } } ], "extra": [ 1, 131, 248, 45, 190, 7, 12, 208, 111, 9, 156, 0, 106, 211, 142, 57, 185, 40, 98, 202, 102, 110, 146, 6, 223, 228, 57, 140, 88, 83, 29, 18, 2, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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