Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 047a6200a29aa93f05e040c247b2a90daefd066da854cdfd6affb75667d40e28

Tx prefix hash: a34fa0c5a1fe11d58361681c7cb727d4bcae59f7adf800f6d3095c30c7c0aeca
Tx public key: c1520375a13ffe01a6af391748d1106da7b78a5cbc7a6e330bf71abe2e2979dc
Timestamp: 1572842643 Timestamp [UTC]: 2019-11-04 04:44:03 Age [y:d:h:m:s]: 06:107:08:50:24
Block: 358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0801 kB
Tx version: 2 No of confirmations: 1479435 RingCT/type: yes/0
Extra: 01c1520375a13ffe01a6af391748d1106da7b78a5cbc7a6e330bf71abe2e2979dc

1 output(s) for total of 0.612089180736 xmr

stealth address amount amount idx tag
00: 9d6eb3b085ebdb59f2a9a34d9588258f45d6384f5f48b0dbb1672874b4472b0c 0.612089180736 306 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": 368, "vin": [ { "gen": { "height": 358 } } ], "vout": [ { "amount": 612089180736, "target": { "key": "9d6eb3b085ebdb59f2a9a34d9588258f45d6384f5f48b0dbb1672874b4472b0c" } } ], "extra": [ 1, 193, 82, 3, 117, 161, 63, 254, 1, 166, 175, 57, 23, 72, 209, 16, 109, 167, 183, 138, 92, 188, 122, 110, 51, 11, 247, 26, 190, 46, 41, 121, 220 ], "rct_signatures": { "type": 0 } }


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