Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a646e6422dfd77b2d9af6026a62e77dbdbee16594bd4b81483c6947c898ef0f3

Tx prefix hash: 9f9e4b5de89cb892ad41d840f86c312ac501635357a439bc264e4690b7eb8eb8
Tx public key: 815b5007b2c13c824f6142954673b9b885c52b650d2e0c9e1eb7c59176a14607
Timestamp: 1579672424 Timestamp [UTC]: 2020-01-22 05:53:44 Age [y:d:h:m:s]: 06:031:14:43:36
Block: 50663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1431496 RingCT/type: yes/0
Extra: 01815b5007b2c13c824f6142954673b9b885c52b650d2e0c9e1eb7c59176a14607021100000003dcee4b4d000000000000000000

1 output(s) for total of 0.417015997267 xmr

stealth address amount amount idx tag
00: 7b769bb6c4a3730d624aeee9033e46754207cf5f39498cb68b91d113cb54f08b 0.417015997267 93938 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 dinastycoin-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": 50673, "vin": [ { "gen": { "height": 50663 } } ], "vout": [ { "amount": 417015997267, "target": { "key": "7b769bb6c4a3730d624aeee9033e46754207cf5f39498cb68b91d113cb54f08b" } } ], "extra": [ 1, 129, 91, 80, 7, 178, 193, 60, 130, 79, 97, 66, 149, 70, 115, 185, 184, 133, 197, 43, 101, 13, 46, 12, 158, 30, 183, 197, 145, 118, 161, 70, 7, 2, 17, 0, 0, 0, 3, 220, 238, 75, 77, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369