Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0418fb9e4ebfc355c484c654092de2da01081a4f87fe280bb32be34e4f4b26d

Tx prefix hash: 67deabd6a94fa949fef3948ac8aed328546c3ddf8379b34fcccbca92e736d591
Tx public key: 9e7b1a79c8d6c8bdae0d643143fbee94298fa81e35cf706cfc0b6b932cc4b92b
Timestamp: 1677694841 Timestamp [UCT]: 2023-03-01 18:20:41 Age [y:d:h:m:s]: 02:034:16:40:59
Block: 707705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 546377 RingCT/type: yes/0
Extra: 019e7b1a79c8d6c8bdae0d643143fbee94298fa81e35cf706cfc0b6b932cc4b92b0211000000025029cbac000000000000000000

1 output(s) for total of 2.773827533000 dcy

stealth address amount amount idx
00: 8b1c7a96a3cd7f23febc306e0b227b5f33238a9b1f58ab8122b87dd27987d5c7 2.773827533000 1151524 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": 707715, "vin": [ { "gen": { "height": 707705 } } ], "vout": [ { "amount": 2773827533, "target": { "key": "8b1c7a96a3cd7f23febc306e0b227b5f33238a9b1f58ab8122b87dd27987d5c7" } } ], "extra": [ 1, 158, 123, 26, 121, 200, 214, 200, 189, 174, 13, 100, 49, 67, 251, 238, 148, 41, 143, 168, 30, 53, 207, 112, 108, 252, 11, 107, 147, 44, 196, 185, 43, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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