Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1b40bac0679f1a290c456d10d33b1588feebf4fd2ec4e6864051c64dee9e8a1

Tx prefix hash: 835cfdedaad87cdb65535905b54d856c9b75bc25d7ee6e35a308d8208a8c83c4
Tx public key: 3f019d334295ffa31fc3a08aacde838bc864e2a1cd21f4b000f44e766263bd10
Timestamp: 1771075410 Timestamp [UTC]: 2026-02-14 13:23:30 Age [y:d:h:m:s]: 00:274:23:13:02
Block: 1477649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202001 RingCT/type: yes/0
Extra: 013f019d334295ffa31fc3a08aacde838bc864e2a1cd21f4b000f44e766263bd10021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5e864d88336fcd5df6c410f2c67926bd36e734b2075d0f0e596f09fba642010d 0.000600000000 1966967 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": 1477659, "vin": [ { "gen": { "height": 1477649 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e864d88336fcd5df6c410f2c67926bd36e734b2075d0f0e596f09fba642010d" } } ], "extra": [ 1, 63, 1, 157, 51, 66, 149, 255, 163, 31, 195, 160, 138, 172, 222, 131, 139, 200, 100, 226, 161, 205, 33, 244, 176, 0, 244, 78, 118, 98, 99, 189, 16, 2, 17, 0, 0, 0, 2, 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: