Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1919fa23fc0598d56b99b4fc127b539a563cb2b9d80b3e68b6c17ec40f11cd75

Tx prefix hash: 478178237629e074205f4c1a3e1437fcde5383adc8e5c8e89984d25210768aa1
Tx public key: a9d89ee81f3f68432e1ecedc71f5e0d566aef2dd9b977cba8bdecf1ef90ebf7d
Timestamp: 1636153293 Timestamp [UTC]: 2021-11-05 23:01:33 Age [y:d:h:m:s]: 05:014:07:23:45
Block: 368161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1313534 RingCT/type: yes/0
Extra: 01a9d89ee81f3f68432e1ecedc71f5e0d566aef2dd9b977cba8bdecf1ef90ebf7d02110000001a745f00f8000000000000000000

1 output(s) for total of 0.036993904670 xmr

stealth address amount amount idx tag
00: ff3da52f00f43692e6554a484e0b7010fa0164775e78d378a336ff4f11c23ac3 0.036993904670 746819 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": 368171, "vin": [ { "gen": { "height": 368161 } } ], "vout": [ { "amount": 36993904670, "target": { "key": "ff3da52f00f43692e6554a484e0b7010fa0164775e78d378a336ff4f11c23ac3" } } ], "extra": [ 1, 169, 216, 158, 232, 31, 63, 104, 67, 46, 30, 206, 220, 113, 245, 224, 213, 102, 174, 242, 221, 155, 151, 124, 186, 139, 222, 207, 30, 249, 14, 191, 125, 2, 17, 0, 0, 0, 26, 116, 95, 0, 248, 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: