Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e19cb149d429147758874ebfa8fb117e905c6aa82231dfab368f464b3d2c175

Tx prefix hash: 19dc3ef7e15a18100b0953fa7060bba27c679ba13c236b45ff075776d10f6d3c
Tx public key: d4b8a1d1d948e454bbcdcf292a8989a7b4f1894a76fe362473cc1a959af8bda2
Timestamp: 1632089637 Timestamp [UTC]: 2021-09-19 22:13:57 Age [y:d:h:m:s]: 05:064:15:23:06
Block: 337141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1346353 RingCT/type: yes/0
Extra: 01d4b8a1d1d948e454bbcdcf292a8989a7b4f1894a76fe362473cc1a959af8bda202110000017f8d0de867000000000000000000

1 output(s) for total of 0.046872687444 xmr

stealth address amount amount idx tag
00: aff26bb5ed2d6992aa53b70302292c1c46967b3e161c9f97ab6e5dbe0a0ab1c2 0.046872687444 694328 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": 337151, "vin": [ { "gen": { "height": 337141 } } ], "vout": [ { "amount": 46872687444, "target": { "key": "aff26bb5ed2d6992aa53b70302292c1c46967b3e161c9f97ab6e5dbe0a0ab1c2" } } ], "extra": [ 1, 212, 184, 161, 209, 217, 72, 228, 84, 187, 205, 207, 41, 42, 137, 137, 167, 180, 241, 137, 74, 118, 254, 54, 36, 115, 204, 26, 149, 154, 248, 189, 162, 2, 17, 0, 0, 1, 127, 141, 13, 232, 103, 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) | monero version: