Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fa7a645e31cb198c2d8572ae34bf2d2210991724814d3e1394e780dcb9af62c

Tx prefix hash: e7113596b0f2d0b2c5f1e6c5a39b4ce561a6738efbc5215a9f4a9a75318a6517
Tx public key: e6aadcd055e18799f84ffd251ed293d7a89d8a376d403d6cc241fc0ab71b05d7
Timestamp: 1707033244 Timestamp [UCT]: 2024-02-04 07:54:04 Age [y:d:h:m:s]: 00:346:14:42:30
Block: 950041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248138 RingCT/type: yes/0
Extra: 01e6aadcd055e18799f84ffd251ed293d7a89d8a376d403d6cc241fc0ab71b05d702110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b2e503df5c69ad6033cf92d037bf9b1d8fd654805f35e45d417f2e5e4dda0cf 0.600000000000 1408595 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": 950051, "vin": [ { "gen": { "height": 950041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b2e503df5c69ad6033cf92d037bf9b1d8fd654805f35e45d417f2e5e4dda0cf" } } ], "extra": [ 1, 230, 170, 220, 208, 85, 225, 135, 153, 248, 79, 253, 37, 30, 210, 147, 215, 168, 157, 138, 55, 109, 64, 61, 108, 194, 65, 252, 10, 183, 27, 5, 215, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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