Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdeed670a03a4c1f47090e7cb37a1ec161ad2cba18a5a410e135acb148ecd2cd

Tx prefix hash: 19f0d189a4beda4cc29973bbdaf13ab5979d656a429d363772a22d75cb315f75
Tx public key: 76cb91bf9e93d7f8d0c9c65a930c4fe1744ef63f06e8a8e2322ea61b3a812a8b
Timestamp: 1767949900 Timestamp [UTC]: 2026-01-09 09:11:40 Age [y:d:h:m:s]: 00:313:18:02:53
Block: 1451945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229652 RingCT/type: yes/0
Extra: 0176cb91bf9e93d7f8d0c9c65a930c4fe1744ef63f06e8a8e2322ea61b3a812a8b021100000002215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8767f747baf80247bb510e220866a80cde66ab2dfec0b8c12e01c2368882fd5b 0.000600000000 1940963 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": 1451955, "vin": [ { "gen": { "height": 1451945 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8767f747baf80247bb510e220866a80cde66ab2dfec0b8c12e01c2368882fd5b" } } ], "extra": [ 1, 118, 203, 145, 191, 158, 147, 215, 248, 208, 201, 198, 90, 147, 12, 79, 225, 116, 78, 246, 63, 6, 232, 168, 226, 50, 46, 166, 27, 58, 129, 42, 139, 2, 17, 0, 0, 0, 2, 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: