Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b627389ede05bb68e43bcdcd9235d6c843a136a10491fe6c720ce3d90efd9eb1

Tx prefix hash: 2c066cf2fac41f8e423386e6a91abe21078f30e0e29467960582c41bd0b348ed
Tx public key: b0707acec62965e85e9cbb7a81834d5843e107c84ef54dca994e158b841e050a
Timestamp: 1685617536 Timestamp [UTC]: 2023-06-01 11:05:36 Age [y:d:h:m:s]: 03:173:10:02:18
Block: 772760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 910176 RingCT/type: yes/0
Extra: 01b0707acec62965e85e9cbb7a81834d5843e107c84ef54dca994e158b841e050a02110000000233af99f4000000000000000000

1 output(s) for total of 0.001688595011 xmr

stealth address amount amount idx tag
00: 306547ebc6ba9636bb99cf7ec4b05d997d55f0ce9ee935e3d1e2e3bd0027b96b 0.001688595011 1222189 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": 772770, "vin": [ { "gen": { "height": 772760 } } ], "vout": [ { "amount": 1688595011, "target": { "key": "306547ebc6ba9636bb99cf7ec4b05d997d55f0ce9ee935e3d1e2e3bd0027b96b" } } ], "extra": [ 1, 176, 112, 122, 206, 198, 41, 101, 232, 94, 156, 187, 122, 129, 131, 77, 88, 67, 225, 7, 200, 78, 245, 77, 202, 153, 78, 21, 139, 132, 30, 5, 10, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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: