Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 197debc04fd7801e1b8632f2568fe076a7eb8ef95b18fe5f2b5c350168eb0a8a

Tx prefix hash: e31986fbc26caf3e19012e043f3e05a0af16ff197fe652612182ebeee4c8a8d9
Tx public key: 0ed129489e4de39419a5fcd4153fa8d2d0d8bd42e93db5707f554e559ed78d60
Timestamp: 1578342454 Timestamp [UCT]: 2020-01-06 20:27:34 Age [y:d:h:m:s]: 04:327:08:27:25
Block: 40006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123317 RingCT/type: yes/0
Extra: 010ed129489e4de39419a5fcd4153fa8d2d0d8bd42e93db5707f554e559ed78d6002110000035c49b77a3d000000000000000000

1 output(s) for total of 452.328301898000 dcy

stealth address amount amount idx
00: e7fb070f5a2fc587965d1e3b6438740ce6a1130a3e6eeb56ae8812fbf26d9e46 452.328301898000 69730 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": 40016, "vin": [ { "gen": { "height": 40006 } } ], "vout": [ { "amount": 452328301898, "target": { "key": "e7fb070f5a2fc587965d1e3b6438740ce6a1130a3e6eeb56ae8812fbf26d9e46" } } ], "extra": [ 1, 14, 209, 41, 72, 158, 77, 227, 148, 25, 165, 252, 212, 21, 63, 168, 210, 208, 216, 189, 66, 233, 61, 181, 112, 127, 85, 78, 85, 158, 215, 141, 96, 2, 17, 0, 0, 3, 92, 73, 183, 122, 61, 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