Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdcea8f2681628fa0838921349b808f773b48dd5b30e7a62db896e7970dea6e8

Tx prefix hash: 0163d099bb9bfd608b29f976e383411fc658347870472a32d023031ca5ae65b3
Tx public key: 740e6f86bcfee2464ff87015a4e73240a9b557760f1ff7a2f5297570f7bb57fe
Timestamp: 1768145714 Timestamp [UTC]: 2026-01-11 15:35:14 Age [y:d:h:m:s]: 00:312:21:41:04
Block: 1453580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229137 RingCT/type: yes/0
Extra: 01740e6f86bcfee2464ff87015a4e73240a9b557760f1ff7a2f5297570f7bb57fe02110000000a215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3db48506746207a2b87e78fbaf2f60c296a99177d7224d55086b92045bba4594 0.000600000000 1942644 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": 1453590, "vin": [ { "gen": { "height": 1453580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3db48506746207a2b87e78fbaf2f60c296a99177d7224d55086b92045bba4594" } } ], "extra": [ 1, 116, 14, 111, 134, 188, 254, 226, 70, 79, 248, 112, 21, 164, 231, 50, 64, 169, 181, 87, 118, 15, 31, 247, 162, 245, 41, 117, 112, 247, 187, 87, 254, 2, 17, 0, 0, 0, 10, 33, 91, 191, 137, 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: