Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ea3768b6cf6a4e023dab85175bd668892bac3ae663fb9df1089d27f55736b4a

Tx prefix hash: 6d13f4177e7625c9e43ffb5195d0d0805d1d65faf6ed9af82fd6a26f1be84621
Tx public key: bf9fc835dae0f572389ddc0dd656b9e4a61d61ef3b273802071fb29d02d1d0d7
Timestamp: 1772677326 Timestamp [UTC]: 2026-03-05 02:22:06 Age [y:d:h:m:s]: 00:172:11:29:39
Block: 1490920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129066 RingCT/type: yes/0
Extra: 01bf9fc835dae0f572389ddc0dd656b9e4a61d61ef3b273802071fb29d02d1d0d7021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 66fe8906dac7a5e5ad416f26c378ce5e8609f22a57402b4ffb6cc38a8a7a961d 0.000600000000 1980432 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": 1490930, "vin": [ { "gen": { "height": 1490920 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66fe8906dac7a5e5ad416f26c378ce5e8609f22a57402b4ffb6cc38a8a7a961d" } } ], "extra": [ 1, 191, 159, 200, 53, 218, 224, 245, 114, 56, 157, 220, 13, 214, 86, 185, 228, 166, 29, 97, 239, 59, 39, 56, 2, 7, 31, 178, 157, 2, 209, 208, 215, 2, 17, 0, 0, 0, 3, 241, 136, 200, 168, 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: