Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cb0e5b84f2ee04c0e04bc41492cd1e677a86fc910df45e40c7c96d03ecf638e

Tx prefix hash: 35ee4910759091df2d9caa98e529aaf8c9df4b1dbda97f5742a58f97e82f21fc
Tx public key: 8e97fe8ff371db7b6b6966aaa5edf2a108f5241c65f6dbcaecdc5734f3658dd9
Timestamp: 1674613008 Timestamp [UCT]: 2023-01-25 02:16:48 Age [y:d:h:m:s]: 02:123:16:02:41
Block: 682151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 610063 RingCT/type: yes/0
Extra: 018e97fe8ff371db7b6b6966aaa5edf2a108f5241c65f6dbcaecdc5734f3658dd90211000000015029cbac000000000000000000

1 output(s) for total of 3.370935961000 dcy

stealth address amount amount idx
00: 10279d99486e5f07c945a7a8bf3df01780b4d0e93dd384b675e926a9bb2279ce 3.370935961000 1124266 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": 682161, "vin": [ { "gen": { "height": 682151 } } ], "vout": [ { "amount": 3370935961, "target": { "key": "10279d99486e5f07c945a7a8bf3df01780b4d0e93dd384b675e926a9bb2279ce" } } ], "extra": [ 1, 142, 151, 254, 143, 243, 113, 219, 123, 107, 105, 102, 170, 165, 237, 242, 161, 8, 245, 36, 28, 101, 246, 219, 202, 236, 220, 87, 52, 243, 101, 141, 217, 2, 17, 0, 0, 0, 1, 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