Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91f14ee4eff61785f682f3a1e83af7b5a532becc75341b8c108ae78358d512b9

Tx prefix hash: 9fbb7c011ee479bacdffb9a0e8bf474e349d70b72e845f06e51fde7f028abebc
Tx public key: b3dea8e32ea5e41187a68e4e369593e8678a772ed8fe5def01d728cedefa5b94
Timestamp: 1674072030 Timestamp [UCT]: 2023-01-18 20:00:30 Age [y:d:h:m:s]: 02:102:00:15:19
Block: 677649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 594600 RingCT/type: yes/0
Extra: 01b3dea8e32ea5e41187a68e4e369593e8678a772ed8fe5def01d728cedefa5b9402110000000152542ceb000000000000000000

1 output(s) for total of 3.488731155000 dcy

stealth address amount amount idx
00: 3042635746fb49e6ddcd5759e90a16d8eaea1793d6c122958b5a7630824783ab 3.488731155000 1119438 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": 677659, "vin": [ { "gen": { "height": 677649 } } ], "vout": [ { "amount": 3488731155, "target": { "key": "3042635746fb49e6ddcd5759e90a16d8eaea1793d6c122958b5a7630824783ab" } } ], "extra": [ 1, 179, 222, 168, 227, 46, 165, 228, 17, 135, 166, 142, 78, 54, 149, 147, 232, 103, 138, 119, 46, 216, 254, 93, 239, 1, 215, 40, 206, 222, 250, 91, 148, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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