Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe6add1ddf7269d122cfd12a0f9d79536b85d8aa45797603f4cf5fde5a3bcd90

Tx prefix hash: 648e1f18f128d86629920d461c47eec3143ff0f3e23674c98fd66d8c997300d9
Tx public key: 7379a99e68c9a78754de060af049793d244c3ef38d1de3121a636e040ea4cafa
Timestamp: 1691807619 Timestamp [UTC]: 2023-08-12 02:33:39 Age [y:d:h:m:s]: 03:096:10:35:45
Block: 823985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 854929 RingCT/type: yes/0
Extra: 017379a99e68c9a78754de060af049793d244c3ef38d1de3121a636e040ea4cafa021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.001142340929 xmr

stealth address amount amount idx tag
00: e85861ca7ecfb34a9e866c1b980df8f159dcd437d4f22d7df9ffa66addf19361 0.001142340929 1276201 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": 823995, "vin": [ { "gen": { "height": 823985 } } ], "vout": [ { "amount": 1142340929, "target": { "key": "e85861ca7ecfb34a9e866c1b980df8f159dcd437d4f22d7df9ffa66addf19361" } } ], "extra": [ 1, 115, 121, 169, 158, 104, 201, 167, 135, 84, 222, 6, 10, 240, 73, 121, 61, 36, 76, 62, 243, 141, 29, 227, 18, 26, 99, 110, 4, 14, 164, 202, 250, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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: