Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f89c84586f2bb399cf114c78604965124003d0150aa48c8f2093270719d773c9

Tx prefix hash: 6cf52edff6d15b53ec69863c566e08ef4886bd88e2881b0db46432861ee91847
Tx public key: 1232c53553e85fc87e5a1f5e1c2b61ee7d34e4070451a64362fbdb27da5ee44a
Timestamp: 1738602040 Timestamp [UTC]: 2025-02-03 17:00:40 Age [y:d:h:m:s]: 01:008:10:51:23
Block: 1211334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264630 RingCT/type: yes/0
Extra: 011232c53553e85fc87e5a1f5e1c2b61ee7d34e4070451a64362fbdb27da5ee44a0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 861dadb42e7c53cde621f82f34f596b32ff4766cecf66f6ffa475cce27716dee 0.000600000000 1698095 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": 1211344, "vin": [ { "gen": { "height": 1211334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "861dadb42e7c53cde621f82f34f596b32ff4766cecf66f6ffa475cce27716dee" } } ], "extra": [ 1, 18, 50, 197, 53, 83, 232, 95, 200, 126, 90, 31, 94, 28, 43, 97, 238, 125, 52, 228, 7, 4, 81, 166, 67, 98, 251, 219, 39, 218, 94, 228, 74, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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