Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfb98eff67436864f1523358e286e5c13f1feed5cb0b7a3cc6279374a3cb3b66

Tx prefix hash: ad3cac72437ae0c19c13d64f235a5a33b28701b05911dcb4a73058ea0c898783
Tx public key: 6a60e00043162180c0575e3a0f7ddb40ff28752d6c7b506e757c2891fa9e5b80
Timestamp: 1572842648 Timestamp [UCT]: 2019-11-04 04:44:08 Age [y:d:h:m:s]: 05:089:02:16:17
Block: 359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0801 kB
Tx version: 2 No of confirmations: 1207834 RingCT/type: yes/0
Extra: 016a60e00043162180c0575e3a0f7ddb40ff28752d6c7b506e757c2891fa9e5b80

1 output(s) for total of 612.084510866000 dcy

stealth address amount amount idx
00: 0cc4a816c8f1ad88a4e5000a8c2724e0dc39ae06f5a0775a9a68033061167077 612.084510866000 307 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": 369, "vin": [ { "gen": { "height": 359 } } ], "vout": [ { "amount": 612084510866, "target": { "key": "0cc4a816c8f1ad88a4e5000a8c2724e0dc39ae06f5a0775a9a68033061167077" } } ], "extra": [ 1, 106, 96, 224, 0, 67, 22, 33, 128, 192, 87, 94, 58, 15, 125, 219, 64, 255, 40, 117, 45, 108, 123, 80, 110, 117, 124, 40, 145, 250, 158, 91, 128 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8