Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7704a8eb4e80bf33c5640d39f5ff17194ab5db33423b6cdcdcefcf4d0e44f0dc

Tx prefix hash: 480d08f11253eb55f9bfa66720599165184e56cdc8c6ce071ab52563358ab921
Tx public key: 83c53d76da4b0da02644c4887453205e71450bfebea754ba71bb69d62d4fd60d
Timestamp: 1734957914 Timestamp [UTC]: 2024-12-23 12:45:14 Age [y:d:h:m:s]: 01:328:04:27:53
Block: 1181475 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498310 RingCT/type: yes/0
Extra: 0183c53d76da4b0da02644c4887453205e71450bfebea754ba71bb69d62d4fd60d02110000000f1f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a8f546c9ffc61a97beaf39d11b5c2afdf3ea1e9d73e43218fcccdf4d5e21fe09 0.000600000000 1667900 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": 1181485, "vin": [ { "gen": { "height": 1181475 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8f546c9ffc61a97beaf39d11b5c2afdf3ea1e9d73e43218fcccdf4d5e21fe09" } } ], "extra": [ 1, 131, 197, 61, 118, 218, 75, 13, 160, 38, 68, 196, 136, 116, 83, 32, 94, 113, 69, 11, 254, 190, 167, 84, 186, 113, 187, 105, 214, 45, 79, 214, 13, 2, 17, 0, 0, 0, 15, 31, 10, 83, 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: