Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 499d9898661394829bb57986c5df34800fb352fbcf309c779f9f705c07ccb535

Tx prefix hash: fa2e3195c68c9899420d1870be94c4c33bf6336cccfe4e3fe60b8ee058827aa1
Tx public key: 4e65f6c631b2b629e6cfc1ae65159c631214d702a9a28a6a3d2b3acbced291d6
Timestamp: 1677061831 Timestamp [UCT]: 2023-02-22 10:30:31 Age [y:d:h:m:s]: 02:003:07:29:54
Block: 702453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 523929 RingCT/type: yes/0
Extra: 014e65f6c631b2b629e6cfc1ae65159c631214d702a9a28a6a3d2b3acbced291d602110000000374b6d784000000000000000000

1 output(s) for total of 2.887230910000 dcy

stealth address amount amount idx
00: f1aadcdad37894f2ee12ca22d1c9f48c2d89a24a851b245e0b70c6fdd600ae29 2.887230910000 1145962 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": 702463, "vin": [ { "gen": { "height": 702453 } } ], "vout": [ { "amount": 2887230910, "target": { "key": "f1aadcdad37894f2ee12ca22d1c9f48c2d89a24a851b245e0b70c6fdd600ae29" } } ], "extra": [ 1, 78, 101, 246, 198, 49, 178, 182, 41, 230, 207, 193, 174, 101, 21, 156, 99, 18, 20, 215, 2, 169, 162, 138, 106, 61, 43, 58, 203, 206, 210, 145, 214, 2, 17, 0, 0, 0, 3, 116, 182, 215, 132, 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