Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f0bba104fb92f26e1f96be80580fa468c71a7cd5dc2bc997dba846c2f0c86db

Tx prefix hash: cf14e2bbac77140722a6b7f4bc7b855453318bc9b1989def8bab94f5ec9a55c1
Tx public key: 9a271722e9ae3c642be7225c95a435aba03857ab4050124adf0594704dc4e50b
Timestamp: 1747872666 Timestamp [UTC]: 2025-05-22 00:11:06 Age [y:d:h:m:s]: 01:181:05:25:40
Block: 1288104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393568 RingCT/type: yes/0
Extra: 019a271722e9ae3c642be7225c95a435aba03857ab4050124adf0594704dc4e50b0211000000021f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9dfaae0d92be489eee30d3fe2e9dbc3ddac1042b0d0155ac27f7e2003a874737 0.000600000000 1775571 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": 1288114, "vin": [ { "gen": { "height": 1288104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9dfaae0d92be489eee30d3fe2e9dbc3ddac1042b0d0155ac27f7e2003a874737" } } ], "extra": [ 1, 154, 39, 23, 34, 233, 174, 60, 100, 43, 231, 34, 92, 149, 164, 53, 171, 160, 56, 87, 171, 64, 80, 18, 74, 223, 5, 148, 112, 77, 196, 229, 11, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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: