Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44ec3a17acba419ff30b89e6337b13e3b7fe49a09c7bcd964509a403120dbe21

Tx prefix hash: 14cf80fb89bf5c96acda8d98cacc3eb96cb278df7e03c832135947bf2b335af1
Tx public key: 1bc4b76c8859b539b171bc888b095ed2e86006579fdb41e08de83c0e7b690ee4
Timestamp: 1771590211 Timestamp [UTC]: 2026-02-20 12:23:31 Age [y:d:h:m:s]: 00:271:03:15:21
Block: 1481915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199303 RingCT/type: yes/0
Extra: 011bc4b76c8859b539b171bc888b095ed2e86006579fdb41e08de83c0e7b690ee4021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 493bd146712506a5e9eb7d0d305f5e55e1881db2d6391ff069f5b8efc04877c3 0.000600000000 1971301 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": 1481925, "vin": [ { "gen": { "height": 1481915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "493bd146712506a5e9eb7d0d305f5e55e1881db2d6391ff069f5b8efc04877c3" } } ], "extra": [ 1, 27, 196, 183, 108, 136, 89, 181, 57, 177, 113, 188, 136, 139, 9, 94, 210, 232, 96, 6, 87, 159, 219, 65, 224, 141, 232, 60, 14, 123, 105, 14, 228, 2, 17, 0, 0, 0, 4, 241, 136, 200, 168, 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: