Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af3e9490e078d003338b96864cb4c320fc2f105cdb16e6827eea941573e28c37

Tx prefix hash: c761cbb82537b8a1d9cf2b3acf85f1b1ca30bec6c8a2b2478a0b301dfa7d9b45
Tx public key: d8f46256dd117e9f56c5e4ffa1cf6a2b7a8b4bd7aec69706434fa8dd88e44bbf
Timestamp: 1578183943 Timestamp [UTC]: 2020-01-05 00:25:43 Age [y:d:h:m:s]: 06:319:18:48:13
Block: 38872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1642460 RingCT/type: yes/0
Extra: 01d8f46256dd117e9f56c5e4ffa1cf6a2b7a8b4bd7aec69706434fa8dd88e44bbf02110000000b8a2ee0d9000000000000000000

1 output(s) for total of 0.456248843642 xmr

stealth address amount amount idx tag
00: a76b482910a7c06be490780b9e3e387c6814957e16061219326cf4bd801629d7 0.456248843642 66603 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": 38882, "vin": [ { "gen": { "height": 38872 } } ], "vout": [ { "amount": 456248843642, "target": { "key": "a76b482910a7c06be490780b9e3e387c6814957e16061219326cf4bd801629d7" } } ], "extra": [ 1, 216, 244, 98, 86, 221, 17, 126, 159, 86, 197, 228, 255, 161, 207, 106, 43, 122, 139, 75, 215, 174, 198, 151, 6, 67, 79, 168, 221, 136, 228, 75, 191, 2, 17, 0, 0, 0, 11, 138, 46, 224, 217, 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: