Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04df560540a63604d9c24eb2b28c3baa5e70faf9d5f97ff658aae950df53c6a0

Tx prefix hash: 0d3fad193d83fc79d8a875d9a83cd35858943d75aa0fc3594c0a5f3dee6c2333
Tx public key: eb4ee1f52edae5a2ebcc696c187754d6b9f28255a19daef3fea266415e4327fd
Timestamp: 1607775421 Timestamp [UCT]: 2020-12-12 12:17:01 Age [y:d:h:m:s]: 03:348:23:01:04
Block: 160607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1000756 RingCT/type: yes/0
Extra: 01eb4ee1f52edae5a2ebcc696c187754d6b9f28255a19daef3fea266415e4327fd02110000002e4ea414e5000000000000000000

1 output(s) for total of 180.242842944000 dcy

stealth address amount amount idx
00: 369b8f26dd01a75f379c4061217eea1539a0f8b83655f23e29b1b36e3b5cd4b4 180.242842944000 283205 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": 160617, "vin": [ { "gen": { "height": 160607 } } ], "vout": [ { "amount": 180242842944, "target": { "key": "369b8f26dd01a75f379c4061217eea1539a0f8b83655f23e29b1b36e3b5cd4b4" } } ], "extra": [ 1, 235, 78, 225, 245, 46, 218, 229, 162, 235, 204, 105, 108, 24, 119, 84, 214, 185, 242, 130, 85, 161, 157, 174, 243, 254, 162, 102, 65, 94, 67, 39, 253, 2, 17, 0, 0, 0, 46, 78, 164, 20, 229, 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