Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb5345cfa53f5ca4140b7fd1a99402f4a6d19761235586a933507ca815c38078

Tx prefix hash: 999c1ba2f70d3bd6b7223b66b0889cafbcdee07a3d67ef05a0b8a133823e6e05
Tx public key: 2e24cb6382ec42604c6a5259b38057f2e97a63852cb97a5d583594be51348610
Timestamp: 1695455949 Timestamp [UCT]: 2023-09-23 07:59:09 Age [y:d:h:m:s]: 01:116:09:00:23
Block: 854265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344468 RingCT/type: yes/0
Extra: 012e24cb6382ec42604c6a5259b38057f2e97a63852cb97a5d583594be513486100211000000054b8f5122000000000000000000

1 output(s) for total of 0.906703899000 dcy

stealth address amount amount idx
00: 8a6e31b8edf803bd7a00802c525927283f2a1f1513b01d1fbcbe677230d084c5 0.906703899000 1308231 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": 854275, "vin": [ { "gen": { "height": 854265 } } ], "vout": [ { "amount": 906703899, "target": { "key": "8a6e31b8edf803bd7a00802c525927283f2a1f1513b01d1fbcbe677230d084c5" } } ], "extra": [ 1, 46, 36, 203, 99, 130, 236, 66, 96, 76, 106, 82, 89, 179, 128, 87, 242, 233, 122, 99, 133, 44, 185, 122, 93, 88, 53, 148, 190, 81, 52, 134, 16, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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