Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1f5a132f886362fd35dff43f173f074fd2fb66b81527afcf1fc22cfa07138be

Tx prefix hash: 460e5390113178135892527d13c2eb93022bac14a0427974ea9143d3fc8d6fe3
Tx public key: b930cff47a4143731bf773c4e5f227d350fd47f5d7e5fb9500d256d6902ea067
Timestamp: 1617369113 Timestamp [UTC]: 2021-04-02 13:11:53 Age [y:d:h:m:s]: 05:043:16:53:28
Block: 231864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1302297 RingCT/type: yes/0
Extra: 01b930cff47a4143731bf773c4e5f227d350fd47f5d7e5fb9500d256d6902ea06702110000006090ec05ad000000000000000000

1 output(s) for total of 0.104649918763 xmr

stealth address amount amount idx tag
00: 8f36c061982c42cae42056b17ea3a47e9b28be2a626b064ded574f8e5f18c955 0.104649918763 481754 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": 231874, "vin": [ { "gen": { "height": 231864 } } ], "vout": [ { "amount": 104649918763, "target": { "key": "8f36c061982c42cae42056b17ea3a47e9b28be2a626b064ded574f8e5f18c955" } } ], "extra": [ 1, 185, 48, 207, 244, 122, 65, 67, 115, 27, 247, 115, 196, 229, 242, 39, 211, 80, 253, 71, 245, 215, 229, 251, 149, 0, 210, 86, 214, 144, 46, 160, 103, 2, 17, 0, 0, 0, 96, 144, 236, 5, 173, 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: