Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb90746b36c0fcb0d2209bc9d5174269b765ccefcf0dd9c7892e4591feb78d17

Tx prefix hash: 1a4c3d6b322428a43d26388d027bc9225686a171dcb6d4d8b5465e2456f9691f
Tx public key: a088d848a5d4d0399bc222a1c68914ae59cfa02ebcc22fa94634e84281247e0f
Timestamp: 1747126775 Timestamp [UTC]: 2025-05-13 08:59:35 Age [y:d:h:m:s]: 01:068:14:39:31
Block: 1281920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301194 RingCT/type: yes/0
Extra: 01a088d848a5d4d0399bc222a1c68914ae59cfa02ebcc22fa94634e84281247e0f0211000000012609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ad6e68782c65141c47d739631045187a8496d81d171714df4b5f0bdd32561f6c 0.000600000000 1769327 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": 1281930, "vin": [ { "gen": { "height": 1281920 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad6e68782c65141c47d739631045187a8496d81d171714df4b5f0bdd32561f6c" } } ], "extra": [ 1, 160, 136, 216, 72, 165, 212, 208, 57, 155, 194, 34, 161, 198, 137, 20, 174, 89, 207, 160, 46, 188, 194, 47, 169, 70, 52, 232, 66, 129, 36, 126, 15, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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: