Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f54d95c4fa5270280c27e820f9e4a002f04c8b4488ed9be32e6e80e10b13f7a

Tx prefix hash: 812bdf72ed58d59dbf73d3e24d6d7c79e8eb2d7a3d10f189be3a717da9d2ca1e
Tx public key: 58fed4e5ff40db77d16e343abdd05da6d1c86667ab2f3f2c9bf03bb572e48244
Timestamp: 1661116348 Timestamp [UCT]: 2022-08-21 21:12:28 Age [y:d:h:m:s]: 02:232:18:48:07
Block: 570916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 687602 RingCT/type: yes/0
Extra: 0158fed4e5ff40db77d16e343abdd05da6d1c86667ab2f3f2c9bf03bb572e4824402110000000175e3f0e9000000000000000000

1 output(s) for total of 7.876230096000 dcy

stealth address amount amount idx
00: bb011c5070bc25f84e5bb903106d1d4d5326c5df4405ecb5a1519561a834265a 7.876230096000 1004114 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": 570926, "vin": [ { "gen": { "height": 570916 } } ], "vout": [ { "amount": 7876230096, "target": { "key": "bb011c5070bc25f84e5bb903106d1d4d5326c5df4405ecb5a1519561a834265a" } } ], "extra": [ 1, 88, 254, 212, 229, 255, 64, 219, 119, 209, 110, 52, 58, 189, 208, 93, 166, 209, 200, 102, 103, 171, 47, 63, 44, 155, 240, 59, 181, 114, 228, 130, 68, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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