Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f211ec3bc52675dc6ffd4ebb277334b24426d02934091c2a4d969a191374200f

Tx prefix hash: 3f104bd50e0c673c31667660a5ac8cad3c98b59d25bd6b6bed3b339eb92af05c
Tx public key: 532f492836e8310bcb7ce81f5baf397ef197b16e445de16ecdb3113ebf6c20d6
Timestamp: 1672874856 Timestamp [UTC]: 2023-01-04 23:27:36 Age [y:d:h:m:s]: 03:134:09:32:32
Block: 667721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 868831 RingCT/type: yes/0
Extra: 01532f492836e8310bcb7ce81f5baf397ef197b16e445de16ecdb3113ebf6c20d602110000000252542ceb000000000000000000

1 output(s) for total of 0.003763250287 xmr

stealth address amount amount idx tag
00: c4933de1579ec608db19b712ad1fbfa818ad64488548b7cdf4e0d40471336fb1 0.003763250287 1108936 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": 667731, "vin": [ { "gen": { "height": 667721 } } ], "vout": [ { "amount": 3763250287, "target": { "key": "c4933de1579ec608db19b712ad1fbfa818ad64488548b7cdf4e0d40471336fb1" } } ], "extra": [ 1, 83, 47, 73, 40, 54, 232, 49, 11, 203, 124, 232, 31, 91, 175, 57, 126, 241, 151, 177, 110, 68, 93, 225, 110, 205, 179, 17, 62, 191, 108, 32, 214, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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: