Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afa0b35b4fd801b66a54ad13427afd6e48d6c3e27be87c8a43400d005f00ab8b

Tx prefix hash: 9805fdc3c2b3efdf3a8a4d9b3517160fe0bda42a5014b5dd53cd896ad0772e86
Tx public key: 015f688e37cdb9b6ce727c5314b8a6c58a3b3ef630aa3d59c10644830d7f7acd
Timestamp: 1711544331 Timestamp [UTC]: 2024-03-27 12:58:51 Age [y:d:h:m:s]: 01:322:13:12:22
Block: 987477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 489152 RingCT/type: yes/0
Extra: 01015f688e37cdb9b6ce727c5314b8a6c58a3b3ef630aa3d59c10644830d7f7acd0211000000030011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c7a4672951e9e051efc2c735ddcc433d4aab5f5c8ab39fa92cd956fed3f58577 0.000600000000 1447728 of 15 -

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": 987487, "vin": [ { "gen": { "height": 987477 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7a4672951e9e051efc2c735ddcc433d4aab5f5c8ab39fa92cd956fed3f58577" } } ], "extra": [ 1, 1, 95, 104, 142, 55, 205, 185, 182, 206, 114, 124, 83, 20, 184, 166, 197, 138, 59, 62, 246, 48, 170, 61, 89, 193, 6, 68, 131, 13, 127, 122, 205, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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