Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa67a50f5ebe17164e44c3b93754476f2fc71087b5fa972e74500eed70ecebce

Tx prefix hash: ca96d2277425bb9046d5897aaef3224a3796f6c04b84e89a344f20f498f04bc1
Tx public key: bf5e5cc00bc75943e531d80e92f1da1d29438ad11231ef547bfeddf2c64ee9ae
Timestamp: 1705978387 Timestamp [UTC]: 2024-01-23 02:53:07 Age [y:d:h:m:s]: 02:301:00:04:14
Block: 941276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 740306 RingCT/type: yes/0
Extra: 01bf5e5cc00bc75943e531d80e92f1da1d29438ad11231ef547bfeddf2c64ee9ae0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1133a8633ba759c84ed1ae5799c98504ae500420c37a438e00ef5069bf8b18a4 0.000600000000 1399422 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": 941286, "vin": [ { "gen": { "height": 941276 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1133a8633ba759c84ed1ae5799c98504ae500420c37a438e00ef5069bf8b18a4" } } ], "extra": [ 1, 191, 94, 92, 192, 11, 199, 89, 67, 229, 49, 216, 14, 146, 241, 218, 29, 41, 67, 138, 209, 18, 49, 239, 84, 123, 254, 221, 242, 198, 78, 233, 174, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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: