Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 212754c861df8d43dd38f03e60e6c2ecbbe658dd254dfee73bc8393f82c7fa3b

Tx prefix hash: 63a958bb75e58e3cd3a459e03b1b16856e79b16c88d7f0c1273bcd0ee26c6964
Tx public key: 12ca483d1980f83e93f4bc953859f3eefe91443ddb07c4582157bc3a12d4027c
Timestamp: 1770217304 Timestamp [UTC]: 2026-02-04 15:01:44 Age [y:d:h:m:s]: 00:284:23:24:38
Block: 1470572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209124 RingCT/type: yes/0
Extra: 0112ca483d1980f83e93f4bc953859f3eefe91443ddb07c4582157bc3a12d4027c021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1f06083387f0feb5d68758257d354206110dc0e6cbbec033aeb3b3c6e8a875bc 0.000600000000 1959840 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": 1470582, "vin": [ { "gen": { "height": 1470572 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f06083387f0feb5d68758257d354206110dc0e6cbbec033aeb3b3c6e8a875bc" } } ], "extra": [ 1, 18, 202, 72, 61, 25, 128, 248, 62, 147, 244, 188, 149, 56, 89, 243, 238, 254, 145, 68, 61, 219, 7, 196, 88, 33, 87, 188, 58, 18, 212, 2, 124, 2, 17, 0, 0, 0, 2, 228, 245, 25, 63, 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: