Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e27be3ddd0cf0121cfdd1b1e6f735ca67d1eb84b6b04f45991a1264c269ac7ae

Tx prefix hash: cec6c5ce0a54de0d179a24228d5132407ed99827cf250794eba4ea72b1e407f6
Tx public key: 0e01e227763697e520d783b6215a2beddec420509a501b6101bc527948f84061
Timestamp: 1578237398 Timestamp [UCT]: 2020-01-05 15:16:38 Age [y:d:h:m:s]: 05:127:14:24:50
Block: 39280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1241108 RingCT/type: yes/0
Extra: 010e01e227763697e520d783b6215a2beddec420509a501b6101bc527948f8406102110000009217786bcf000000000000000000

1 output(s) for total of 454.830838164000 dcy

stealth address amount amount idx
00: 3793f7f8eed9853243f1c9d93c14d73ab834d541e12eaf74309cf1ae1f0c24a5 454.830838164000 67612 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": 39290, "vin": [ { "gen": { "height": 39280 } } ], "vout": [ { "amount": 454830838164, "target": { "key": "3793f7f8eed9853243f1c9d93c14d73ab834d541e12eaf74309cf1ae1f0c24a5" } } ], "extra": [ 1, 14, 1, 226, 39, 118, 54, 151, 229, 32, 215, 131, 182, 33, 90, 43, 237, 222, 196, 32, 80, 154, 80, 27, 97, 1, 188, 82, 121, 72, 248, 64, 97, 2, 17, 0, 0, 0, 146, 23, 120, 107, 207, 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