Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2d11fca319c5d91f051a1cfdd97060363ac0a486a8ed873db6d420adfcd77fe

Tx prefix hash: 4b2f7db74c08eeb93360379a2d08f53c1b780caf8d711e4294e9becc3acabaea
Tx public key: af5b5cfbb21a1fa1e949e54769b2fa718a3db7f71b0697a1a6a3d3bb030a1a58
Timestamp: 1637136895 Timestamp [UTC]: 2021-11-17 08:14:55 Age [y:d:h:m:s]: 05:006:15:31:24
Block: 376096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1308054 RingCT/type: yes/0
Extra: 01af5b5cfbb21a1fa1e949e54769b2fa718a3db7f71b0697a1a6a3d3bb030a1a58021100000016e9564d6f000000000000000000

1 output(s) for total of 0.034820757414 xmr

stealth address amount amount idx tag
00: 8ced8b7c8f48385ac9496a42f2c3b531217ea9d558576a149bcfa2df11ce472a 0.034820757414 760854 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": 376106, "vin": [ { "gen": { "height": 376096 } } ], "vout": [ { "amount": 34820757414, "target": { "key": "8ced8b7c8f48385ac9496a42f2c3b531217ea9d558576a149bcfa2df11ce472a" } } ], "extra": [ 1, 175, 91, 92, 251, 178, 26, 31, 161, 233, 73, 229, 71, 105, 178, 250, 113, 138, 61, 183, 247, 27, 6, 151, 161, 166, 163, 211, 187, 3, 10, 26, 88, 2, 17, 0, 0, 0, 22, 233, 86, 77, 111, 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: