Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33bb2cd74aa55f0fd5686158792537f99d8294fcac3f9f879e5e81b8396f1fa4

Tx prefix hash: d76309dc2cae85fe804e3b751bf03fc5f63a647b4db9958543b8c204994b2c25
Tx public key: 868e415113e97c2f0eb12523fcb239f4cad15b431253a2d588f57776eacdbd5f
Timestamp: 1697432068 Timestamp [UCT]: 2023-10-16 04:54:28 Age [y:d:h:m:s]: 01:211:14:43:58
Block: 870659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 412301 RingCT/type: yes/0
Extra: 01868e415113e97c2f0eb12523fcb239f4cad15b431253a2d588f57776eacdbd5f02110000000133af99f4000000000000000000

1 output(s) for total of 0.800101955000 dcy

stealth address amount amount idx
00: c72e7c96fcf4dce41d8c28ad414400ac360099fa9669b1c7db9f9ecfb120310e 0.800101955000 1325542 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 dinasty-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": 870669, "vin": [ { "gen": { "height": 870659 } } ], "vout": [ { "amount": 800101955, "target": { "key": "c72e7c96fcf4dce41d8c28ad414400ac360099fa9669b1c7db9f9ecfb120310e" } } ], "extra": [ 1, 134, 142, 65, 81, 19, 233, 124, 47, 14, 177, 37, 35, 252, 178, 57, 244, 202, 209, 91, 67, 18, 83, 162, 213, 136, 245, 119, 118, 234, 205, 189, 95, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8