Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50cb988766e7f2e8c70125816d07c53aeb0cde4d36f2756805ffe44409e06278

Tx prefix hash: 0b88f211dd398a218b6161d9bebdd175e09d03fa125ea69a412c1ee2f7d4333c
Tx public key: e1e209fe68cfe54e81d75561fbe90bb720a4b5e03ccfebf85e08d16d5050c2db
Timestamp: 1637018852 Timestamp [UCT]: 2021-11-15 23:27:32 Age [y:d:h:m:s]: 03:184:01:19:14
Block: 375145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 910111 RingCT/type: yes/0
Extra: 01e1e209fe68cfe54e81d75561fbe90bb720a4b5e03ccfebf85e08d16d5050c2db021100000026e59f5d07000000000000000000

1 output(s) for total of 35.074320946000 dcy

stealth address amount amount idx
00: 9b31606e094548b7327d1baf9548fec538e19c6a4bca3eff98777523e7f9237a 35.074320946000 759135 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": 375155, "vin": [ { "gen": { "height": 375145 } } ], "vout": [ { "amount": 35074320946, "target": { "key": "9b31606e094548b7327d1baf9548fec538e19c6a4bca3eff98777523e7f9237a" } } ], "extra": [ 1, 225, 226, 9, 254, 104, 207, 229, 78, 129, 215, 85, 97, 251, 233, 11, 183, 32, 164, 181, 224, 60, 207, 235, 248, 94, 8, 209, 109, 80, 80, 194, 219, 2, 17, 0, 0, 0, 38, 229, 159, 93, 7, 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