Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be108d1eb4440bc9dcd3f730f6466bf73586cea2e1d55feba0a1d4f64f4a53ea

Tx prefix hash: 05c0c38c00bbef98b4f80da7992df3730a1683e600346e40cb427f252b913b73
Tx public key: 4be8027124e5a6ae53913711500aa91aa0c2ba47d9cfa109204e2a7ca002c226
Timestamp: 1577724393 Timestamp [UCT]: 2019-12-30 16:46:33 Age [y:d:h:m:s]: 04:363:14:24:45
Block: 35167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1148965 RingCT/type: yes/0
Extra: 014be8027124e5a6ae53913711500aa91aa0c2ba47d9cfa109204e2a7ca002c2260211000000014943cd9f000000000000000000

1 output(s) for total of 469.329642947000 dcy

stealth address amount amount idx
00: 6aa852430c657cf05d7ae741e923400138a77d6fcf32014f4cca77c2861bfa7a 469.329642947000 59239 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": 35177, "vin": [ { "gen": { "height": 35167 } } ], "vout": [ { "amount": 469329642947, "target": { "key": "6aa852430c657cf05d7ae741e923400138a77d6fcf32014f4cca77c2861bfa7a" } } ], "extra": [ 1, 75, 232, 2, 113, 36, 229, 166, 174, 83, 145, 55, 17, 80, 10, 169, 26, 160, 194, 186, 71, 217, 207, 161, 9, 32, 78, 42, 124, 160, 2, 194, 38, 2, 17, 0, 0, 0, 1, 73, 67, 205, 159, 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