Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9dc209e9c42655b6b593ea0d45b63eba0f7acd6a6088467773005f5584151d9e

Tx prefix hash: a0021d0b865f8b444d65312033e06b572a5a651e4861c398c8374fa1cb62698e
Tx public key: b3c4fbc6acb8b960bb8b9348753d2ec538a97eb08d39e482521c88df65781044
Timestamp: 1580623172 Timestamp [UCT]: 2020-02-02 05:59:32 Age [y:d:h:m:s]: 05:032:02:29:53
Block: 56968 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1174865 RingCT/type: yes/0
Extra: 01b3c4fbc6acb8b960bb8b9348753d2ec538a97eb08d39e482521c88df65781044021100000001ff58ae94000000000000000000

1 output(s) for total of 397.413110518000 dcy

stealth address amount amount idx
00: a59494805f19a5d0bee586801c4e7b2065ed4f58ce0debff652ba655b9d658d3 397.413110518000 105031 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": 56978, "vin": [ { "gen": { "height": 56968 } } ], "vout": [ { "amount": 397413110518, "target": { "key": "a59494805f19a5d0bee586801c4e7b2065ed4f58ce0debff652ba655b9d658d3" } } ], "extra": [ 1, 179, 196, 251, 198, 172, 184, 185, 96, 187, 139, 147, 72, 117, 61, 46, 197, 56, 169, 126, 176, 141, 57, 228, 130, 82, 28, 136, 223, 101, 120, 16, 68, 2, 17, 0, 0, 0, 1, 255, 88, 174, 148, 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