Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3813532b47c7796f134018b752c03f3e4f5191818db5bfee63ead5125b16cc22

Tx prefix hash: b28efff28150d6db79951875c9c96f852ed2224430a8dd09ee91bae3d69690e2
Tx public key: e98b8fde39f2e01e73e021c88a12f5059ca2733d534c5f320f1c44e9c5edf8d0
Timestamp: 1706174044 Timestamp [UCT]: 2024-01-25 09:14:04 Age [y:d:h:m:s]: 01:287:07:34:44
Block: 942907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 464155 RingCT/type: yes/0
Extra: 01e98b8fde39f2e01e73e021c88a12f5059ca2733d534c5f320f1c44e9c5edf8d002110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2aad4eb37ed6dcb83e2603411efd6530587b20700418bdfa519617e4f70ca4a 0.600000000000 1401087 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": 942917, "vin": [ { "gen": { "height": 942907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2aad4eb37ed6dcb83e2603411efd6530587b20700418bdfa519617e4f70ca4a" } } ], "extra": [ 1, 233, 139, 143, 222, 57, 242, 224, 30, 115, 224, 33, 200, 138, 18, 245, 5, 156, 162, 115, 61, 83, 76, 95, 50, 15, 28, 68, 233, 197, 237, 248, 208, 2, 17, 0, 0, 0, 6, 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